SAP Logistics

Based on SAP Note -  2590037 - Output Management for Deliveries Output control for delivery documents is still based on the former SD output control framework (NACE) The new output management framework is not yet supported for delivery documents in SAP S/4HANA. Path to configure Output Control for Deliveries You configure output control in the Implementation Guide (IMG) under Logistics Execution →  Shipping → Basic Shipping Functions → Output Control.

At times, We might require to enhance the item segment of the Standard Purchase Order confirmation IDoc type 'ORDERS05' which requires two activities to be performed in this situation: Append the new field to the segment Populating values in the fields during IDoc processing Append field in the segment The custom field is required to be appended to the item segment field 'EIEDP01' which is a structure through append structure functionality in SE11 Populating values in the fields during IDoc processing Populating values in the custom field related to the item segments of the purchase order 'E1EDP01' will be accomplished through the customer exit 'EXIT_SAPLEINM_002' Thank you.

Per SAP Note - 2420306, There are no change documents for the transfer order tables LTAK and LTAP. Transactions to create/confirm transfer orders will update tables CDHDR and CDPOS in the event that certain other documents are changed - e.g. if a delivery is changed (CDHDR object class 'LIEFERUNG') or if a batch is changed (object class 'CHARGE') or if a handling unit is involved (object class 'HANDL_UNIT').                                                  This is because deliveries, handling units and batches can have multiple changes and therefore require a change history; whereas a WM transfer order is transactional. A transfer order is simply created then confirmed - there is no editing, therefore the transfer order includes the changes within its own document data.                                         Therefore, if you wish to check change logs relating to a WM document, you could

This post explains how database update can be performed through transaction codes SE16N and SE16. At times, there might be a situation in the test environment where we are required to perform database updates in order to manipulate or try to replicate a case in a lower environment. Database contents in SAP can be viewed through transaction codes SE16N or SE16. This post explains how the database update can be performed for both transaction codes through debug mode. Case 1: Transaction Code SE16 In this case, I have taken a sample example to update the VBAK table entry through debug mode. Enter Sales Order Number Select the entry displayed enter '/H' in the command bar and click on ok or enter button. Then click on entering again after debugging activation to enter into debugging screen Click on the 'Code' then display as 'SHOW' on the right side of the screen. Then we will change it to 'EDIT' as we are trying to change th

The CDHDR and CDPOS table contains information related to changes of a specific entity. Using these tables you can track how many times the value of an entity has changed and especially to which value. Because the CDHDR and CDPOS tables contain a lot of data it is advisable to restrict the table during data extraction. Using a restriction on OBJECTCLASS you have the ability to only select those records related to a specific SAP entity for e.g. Sales Orders (VERKBELEG), Purchase Orders (EINKBELEG) or Handling Units (HANDL_UNIT).  To determine which filter must be set up the table TCDOBT can be used. This table stores all object classes available in the system .

Business at times looks to perform few activities post TO confirmation automatically. In this case, the Support team can make use of below Exit. This exit will trigger only during the update. Customer Exit - EXIT_SAPLL03T_001,EXIT_SAPLL03T_002,EXIT_SAPLL03T_003 Thank you.

Mass confirmation of TO's can be done through warehouse monitor but whereas confirmation through LT23 require the business user to confirm each Transfer Order manually Below are the process steps to be followed for mass confirmation of TO's. Batch Job needs to be set up for report RLLL01SE so that n order to refresh the list of unconfirmed TOs every 15 min. Then run LL01 : Select "unconfirmed TO" + select the TOs to confirm in mass by their movement type (double click on the lines you want to confirm until you have the TO list) Select the TOs to be confirmed and do "Go to" + "confirm TO in background"