SAP Logistics

 Below are the commonly used exits at shipment document level EXIT_SAPLV56U_003 is used for handling number ranges i.e, sometimes there will be a requirement to have the same shipment number as that of the DWM in that case, you can leverage this exit EXIT_SAPLV56U_004 is used to write custom functionality or validations based on the shipment status

There will be different procurement processes like Standard PO, Framework PO, Services, and STO... but do understand that the "Manage Purchase Order" app will support only the standard PO document types or Z document types created with reference to standard PO document type 'NB' without changing parameters. In this situation, you have to go with the "Create Purchase order" app to create purchase orders for other processes.

 At times, business requires specific requirements where we cannot use the standard picking strategies which SAP has provided. In this situation, customer exit 'EXIT_SAPML03T_003' need to be leveraged to accomplish the requirement to derive picking strategy in a custom manner.

************************************************** Material   Material basic data - MARA  Material Plant level data - MARC  Material Sales level data - MVKE  Material valuation data - MBEW  Material warehouse data - MLGN  Material/Batch data - MCH1  Plant/Material/Batch data - MCHA  Material stock data - MARD Material batch stocks - MCHB Material valuation data history - MBEWH Material stock data history - MARDH ********************************************** Transport  Transport Header Data - E070 Transport data view on objects - E071V *********************************************** Background Job table - TBTCP ************************************************ Idocs table  IDOC control record - EDIDC IDOC data record - EDID4 IDOC status record - EDIDS ************************************************     

Below is the BAPI to be used for converting from one currency to another currency based on the exchange rate on a specific date. Below are the parameters to be passed to fetch the required information.   CALL  FUNCTION  'BAPI_EXCHANGERATE_GETDETAIL'        EXPORTING         rate_type   = <Exchange rate type >         from_curr   = <From Currency>         to_currncy  = < 'Currency'>          date        = < Date >        IMPORTING         exch_rate   =  < >          return      = < >     

 As per standard SAP, storage location cannot be determined automatically at the sales order level. At times, there will be a requirement where businesses want storage location to be determined automatically at the sales order level. Follow the below steps to accomplish the requirement. 1. Create a new custom table to maintain the combination or parameters of storage location determination 2. write the logic in the Include MV45AFZB, EXIT : USEREXIT_CHECK_VBAP to call at sales order level

At times, businesses will ask for a report based on the table extract of single or multiple tables. As this is a direct table extract, we need not take the help of a developer to extract the data from the tables. SAP has given a provision to generate this kind of report by functional consultants rather than taking the help of the technical team. This report extracts by the functional team will be done with the help of SQVI and SQ01 queries. SQVI query created by a user cannot be accessed by another user ( User Dependent) SQ01 query created by a user can be accessed by other users based on the user group ( User Independent) SQVI queries in general will be generated by the business and consultants will mostly assist business users. But at times, consultants use the SQVI query to extract specific data in a quick way as per business needs and then subsequently extract them to excel and provide the required information to business users. If business insists on the query access for the SQVI,