Skip to main content

Posts

[WM] Exit for Stock removal strategy

 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.

Commonly used tables in SAP SD & MM

************************************************** 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 ************************************************     

BAPI for currency conversion and exchange rate calculation

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      = < >     

[SAP SD] Storage location determination at sales order level

 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

SQVI Query

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,...

[SAP SD] Route determination at sales order level

Ideally, the route will be determined based on the below standard configuration at the sales order level. Standard SAP  The route  is determined automatically in the sales order based on:   Departure zone or country of the Delivering Plant Destination zone or country of the Ship-to Party Shipping condition from the Sold-to Party Customer master Transportation group from Material Master Custom But however, there are situations where standard SAP parameters cannot be used for route determination due to business constraints.  In this situation, SAP has provided an exit 'EXIT_SAPL0VRF_001' to accomplish custom requirements of route determination where businesses can maintain their own determinations.

16 steps of pricing procedure - SAP SD , MM

Below are the 16 steps of the pricing procedure : Step  - It depicts condition type sequence similar to Sl.No Counter - it's a substep  Condition type - Pricing elements are represented as a condition type  Description - this field displays description of the condition type From, To    - From, and To  covers the Steps to be considered during condition value calculation  Manual - if we select this, condition type should be manually entered in the document Required - if we select this, the system will not allow you to save the document until it is entered Statistical - if we select this, the Specific condition value doesn't have any impact during the price calculation Print - if the specific condition type should be printed or not will be controlled in this field SubTotal - It's used for temporary storage and can be subsequently used in other calculations Alternate Calculation type - if the condition value should be derived based on a specific ...