SAP Logistics

Standard SAP doesn't control the change of quantity at inbound delivery due to this business user will have a provision to increase the quantity of the inbound delivery to that of Purchase order quantity. This will be commonly seen when an inbound delivery gets created through IDoc, System by default will create for the quantity received rather than validating against the PO which will be quite confusing for the buyer and receiving department. To restrict this, SAP  has provided message control functionality. Below is the process steps to achieve this. AS IS Config Changes at Message Control Level After Change Increase the Inbound delivery quantity to that of PO quantity then system will throw an error message as stated below Thank You.

At times, you might require finding a BADI on a screen and in this situation, we can leverage of Object Type - 'CL_EXITHANDLER' to find the list of BADI's available on the screen. In order to access this object type, we need to use T.Code - SE24 class builder.       Click on display and select method 'GET_INSTANCE'  to enter the method. put a breakpoint at    ' CALL  METHOD  cl_exithandler => get_class_name_by_interface' Then go to the required screen where exit needs to be identified. For instance, here I have executed T.Code VA01 then BADI's relevant to the initial screen will be displayed . To view the relevant BADI's click on Exit_Name parameter of Method. Then click on F8 or execute to go to the next available BADI on the screen and if no BADI exist then the screen will be displayed. Ensure to remove breakpoint upon completion of the required task else breakpoint will be triggered for all sc...

At times, We might have released TR by mistake to subsequent environment or Quality and require to change the description of a Transport request. SAP has given a provision to change the description even after TR release. Below process steps depict the process to be followed to do so. Enter the TR number for which description need to be changed Select the parent request for which description need to be changed Once the parent request is selected double click on the required TR to change the description. A popup will be displayed upon selecting the required TR Click on the change Icon of the popup to change the TR description Thank you...

Per Standard SAP, Cost Center description will not appear in the Purchase Requisition or Purchase Order but there might be instances where the business user wishes to display cost centre description when cost centre is maintained at PR or PO level. Below configuration settings need to be performed to achieve this. 1. Goto T.Code OXK1 - Maintain coding block subscreens : Overview Create a customer subscreen starting with 9*  will all the fields in account assignment screen. System ideally fetches the screen no which matches with all the fields. So in the below case I am creating a subscreen with the all the necessary account assignment fields and generate the screen. Enable Text field for cost centre. Business Process: Create an account assignment purchase order and you could notice that cost centre description getting displayed.

At times, business requires creating a PO automatically upon goods receipt. Below are the settings needs to be done to accomplish this requirement. Config Settings: Maintain Auto PO check at Movement Type level. : Master Data Settings: Maintain Auto PO enabled at Vendor Master Data Level. Business Process: 1.        Perform Goods receipt using Movement Type 101         Enter Material, Plant, Vendor and other required details during Goods Receipt.          Perform Goods Receipt and then go to the display to display mode to view PO details.                    PO details would appear in the Purchase Order Data Tab of MIGO Screen.                 

There might be situations where business require user to restrict PO creation if PR doesn't exist. This can be done at functional authorization level. Step 1 : Goto SPRO --> Purchasing ----> Authorisation Management Step 2: Uncheck W/O reference and check Ref to Purchase Requisition Step 3: Assign Parameter ‘EFB’ to business user Now if you try to create  Purchase Order without referring to Purchase Requisition then below error will be displayed.