Automate

Hi all,

I'm quite new to WinShuttle (and fora) so might be missing something simple, but:
I'm looking into production orders (wanting the PO header nr.) with a certain PO-item status (i.e. no active DLV or TECO status). However, filtering on status doesn't work (prob. due to linking to a non-key field and filtering on the linked table) and I have to resort to retrieving ALL of the PO's, within say a week, and filtering the hoot out of the output using Excel formulas.
This works, but the Excel-file is unusually large (60-70K rows) for how much info I actually want out of it (200-300 rows).

Do you know any tips and tricks on how to keep your output as manageable as possible, using WS Query? Especially when having to resort to status filters, which means filtering on a table field that doesn't link to the rest via a key viald (i.e. JEST-STAT via OBJNR to AUFK and AFKO).

Happy to elaborate by the way; haven't found the most effective question format :) 

P.S. in this case looking for the answer to 'What PO's contain un-delivered, un-TECO'd items within a certain Basic Finish Time window'? 
Used tables/fields: AFKO (MATNR), AUFK, JEST
Criteria on: AFKO-GLTRP, JEST-STAT&JEST-INACT

------------------------------
Robbert Lobik | Supply Chain Analyst
Bakker International BV
------------------------------

Hi Robbert,

In general terms, I start putting together a query and keep testing the output, doing a record count and viewing the output.  If you do that frequently, you'll know when things are good or not.  I also tend to output a lot of fields if I'm getting a lot of output and not familiar with the tables, so that I can see if there are differences, such as effectivity dates, deletion codes, status, etc.

I don't have many queries built related to product orders.  I do understand that checking the status field and joining on non-key fields is not ideal.  Sometimes SAP doesn't make it easy. 

When that happens, I also look for infosets and logical databases to see if there are better ways to get to the output, as well as BAPIs, and also for any reports SAP may generate as a last resort.  You can record exporting report data, but it typically requires GUI scripting when selecting where to save it, although not always.

Best Regards,
Sigrid

------------------------------
Sigrid Kok
PSE | Winshuttle NA
------------------------------

Original Message:
Sent: 05-22-2020 08:19
From: Robbert Lobik
Subject: How to keep query-output manageable?

Hi all,

I'm quite new to WinShuttle (and fora) so might be missing something simple, but:
I'm looking into production orders (wanting the PO header nr.) with a certain PO-item status (i.e. no active DLV or TECO status). However, filtering on status doesn't work (prob. due to linking to a non-key field and filtering on the linked table) and I have to resort to retrieving ALL of the PO's, within say a week, and filtering the hoot out of the output using Excel formulas.
This works, but the Excel-file is unusually large (60-70K rows) for how much info I actually want out of it (200-300 rows).

Do you know any tips and tricks on how to keep your output as manageable as possible, using WS Query? Especially when having to resort to status filters, which means filtering on a table field that doesn't link to the rest via a key viald (i.e. JEST-STAT via OBJNR to AUFK and AFKO).

Happy to elaborate by the way; haven't found the most effective question format :)

P.S. in this case looking for the answer to 'What PO's contain un-delivered, un-TECO'd items within a certain Basic Finish Time window'?
Used tables/fields: AFKO (MATNR), AUFK, JEST
Criteria on: AFKO-GLTRP, JEST-STAT&JEST-INACT

------------------------------
Robbert Lobik | Supply Chain Analyst
Bakker International BV
------------------------------

Hi Sigrid,

Thanks a lot, very helpful! Once more unto the breach, then.

Best regards,
Robbert

------------------------------
Robbert Lobik | Supply Chain Analyst
Bakker International BV | 0622780604
------------------------------

Original Message:
Sent: 06-03-2020 09:24
From: Sigrid Kok
Subject: How to keep query-output manageable?

Hi Robbert,

In general terms, I start putting together a query and keep testing the output, doing a record count and viewing the output.  If you do that frequently, you'll know when things are good or not.  I also tend to output a lot of fields if I'm getting a lot of output and not familiar with the tables, so that I can see if there are differences, such as effectivity dates, deletion codes, status, etc.

I don't have many queries built related to product orders.  I do understand that checking the status field and joining on non-key fields is not ideal.  Sometimes SAP doesn't make it easy.

When that happens, I also look for infosets and logical databases to see if there are better ways to get to the output, as well as BAPIs, and also for any reports SAP may generate as a last resort.  You can record exporting report data, but it typically requires GUI scripting when selecting where to save it, although not always.

Best Regards,
Sigrid

------------------------------
Sigrid Kok
PSE | Winshuttle NA

Original Message:
Sent: 05-22-2020 08:19
From: Robbert Lobik
Subject: How to keep query-output manageable?

Hi all,

I'm quite new to WinShuttle (and fora) so might be missing something simple, but:
I'm looking into production orders (wanting the PO header nr.) with a certain PO-item status (i.e. no active DLV or TECO status). However, filtering on status doesn't work (prob. due to linking to a non-key field and filtering on the linked table) and I have to resort to retrieving ALL of the PO's, within say a week, and filtering the hoot out of the output using Excel formulas.
This works, but the Excel-file is unusually large (60-70K rows) for how much info I actually want out of it (200-300 rows).

Do you know any tips and tricks on how to keep your output as manageable as possible, using WS Query? Especially when having to resort to status filters, which means filtering on a table field that doesn't link to the rest via a key viald (i.e. JEST-STAT via OBJNR to AUFK and AFKO).

Happy to elaborate by the way; haven't found the most effective question format :)

P.S. in this case looking for the answer to 'What PO's contain un-delivered, un-TECO'd items within a certain Basic Finish Time window'?
Used tables/fields: AFKO (MATNR), AUFK, JEST
Criteria on: AFKO-GLTRP, JEST-STAT&JEST-INACT

------------------------------
Robbert Lobik | Supply Chain Analyst
Bakker International BV
------------------------------