/SCWM/R_TEST_TW_CONDTECH - Transit Warehouse - Check Destination Bin DeterminationPERFORM Short Reference PERFORM Short Reference
This documentation is copyright by SAP AG.
You can use this report to simulate the determination of condition records used for destination bin determination upon warehouse task creation for transit handling units (HUs) or HU containers in transit warehousing.
This report assists you in verifying the setup of your condition records.
The setup of the destination bin determination used during warehouse task creation in transit warehousing is based on condition records for application TWP and usage TW.
You have maintained condition records using transaction Maintain Conditions.
You have maintained a CSV file containing the information about the expected result for the destination bin determination. The character ";" is used as separator.
The file needs to have the following structure:
- In the first row, you can enter textual descriptions of the components used in the second row. This entry is not mandatory, it is just for your orientation. But note that a first row needs to exist.
- In the second row, you have to enter component names of the following structures for fields influencing the bin to be determined:
- Component CONTAINER_HU in order to define if the simulation should run for a HU container or a transit HU
- And enter the component name of the following structure for the expected results:
- In the subsequent rows, enter the values for the components. The values need to be entered in external format. For component CONTAINER_HU, you need to enter an 'X' if the simulation for this line should run for an HU container or ' ' if the simulation is for a transit HU.
For more information, see Example.
You can upload the created CSV file containing the expected results for destination bin determination. After uploading the file, you can start the simulation of the determination and the system highlights differences between the expected results and the system setup. After a simulation, the simulation log provides additional information about how the results are determined and which access sequence and condition table entries are used.
When using the CSV file for testing the setup of bin determination in transit warehousing, there is no need to have business data (for example, freight orders) already in the system, except the data used in condition tables (for example, regions, storage types).
If you already have processes up and running and you want to analyze the bin determination after the fact, you can check the application log for object /SCWM/WME for the warehouse tasks using transaction
Analyse Application Log. In the long text of
message /SCWM/TW_WT012 "Check long text for characteristics used to determine condition records", you
can find the details about the characteristics used. For this, the log needs to be active with the No Info. checkbox deselected in transaction
Activate Application Log for EWM Applications.
If you want to run the simulation for a specific warehouse number only, enter the warehouse number in the Warehouse Number field.
Select or enter the file name of the CSV file containing the data for which you want to simulate the bin determination.
Having done this, choose Upload to upload the file to the transaction. If you have entered a warehouse number, only the entries that correspond to that warehouse number are uploaded.
After you have chosen Upload, the system displays the data of the CSV file.
Now you can use Start Simulation or Start Simulation for Selected Row to run the simulation of the bin determination, either for all lines or for the selected one. After simulation, the Status icon is adjusted according to the result and if the result is as expected. You can then select the Expected Results and Simulation Results checkboxes in the lower part of the screen or use Display Simulation Log to get more details about the way the system is running the determination.
You can use Hide Unused Columns to check quickly which data is not considered at all during the determination, for example, if there is no condition table in the access sequence making use of the component TWP_SHIPPER Shipper, the column is no longer displayed. This function can be used only after you have simulated the determination.
If the expected result is not the same as the result from the simulation, you can use the Spreadsheet Row column in the Expected Result to perform a quick check on the CSV file to see if the data in the file is not as intended.
The following CSV data is an example for the required structure with a description line, a component names line, and 2 lines of business data. You can copy the data to a local file on your computer and save it as a CSV file.
This example does not use all available columns.
HU Container;Warehouse Number;Consignee;Consignee Country Key;Consignee Region;Final Transit Warehouse
Location Number;Final Transit Warehouse Country Key;Final Transit Warehouse Region;Next Unloading Location
Number;Next Unloading Location Country Key;Next Unloading Location Region;Warehouse Process Type;Activity;Dangerous
Goods Indicator;High Value Goods Indicator;Oversize Goods Indicator;To be Clarify Indicator;Warehouse
Door;Warehouse Process Category;Transport Category;Packing Group;Main Carrier;Damaged Cargo;Previous
Transit Warehouse Location Number;Previous Transit Warehouse Country;Previous Transit Warehouse Postal
Code;Previous Transit Warehouse Region;Condition Sequence Number;Destination Storage Type;Destination Storage Section;Destination Storage Bin;Destination Storage Bin Type
CONTAINER_HU; TWP_LGNUM;TWP_COEE;TWP_COEE_CTRY;TWP_COEE_REGI;TWP_LTW_LOC;TWP_LTW_CTRY; TWP_LTW_REGI;TWP_NTW_LOC; TWP_NTW_CTRY;TWP_NTW_REGI;TWP_PROCTY;TWP_PROCTY_ACTTY;TWP_DA_GOODS; TWP_HV_GOODS;TWP_OS_GOODS;TWP_TO_CLARIFY;TWP_DOOR;TWP_PROCTY_TRART;TWP_DG_CARR_TYPE; TWP_DG_PGRO;TWP_MCARR;TWP_DAMAGED; TWP_PTW_LOC;TWP_PTW_CTRY;TWP_PTW_POCO;TWP_PTW_REGI;TWP_COND_SEQ;TWP_DEST_LGTYP; TWP_DEST_LGBER;TWP_DEST_LGPLA;TWP_DEST_LPTYP
;JPTY;OAF-CO-03;US;CA;OAF-STA-USPHX;US;AZ;AF-GW-JPNRT;JP;12;P360;PTWY; ;X; ;X;D001;1;;;;;;;;;;H970;;CL-ZONE;
General Data in Customer Master General Data in Customer Master
This documentation is copyright by SAP AG.
Length: 7844 Date: 20200226 Time: 011948 sap01-206 ( 41 ms )
Looking for Support? Questions?
Leave us your contact details and we will call you back. Panels marked with * are mandatory.