SAP Logistics

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,

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.

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 calculation and not th

At times, businesses will come up stating that physical inventory is performed for wrong quantities and require reversal for the difference posting happened. In this situation, the business has to perform physical inventory again, the system will never allow you to reverse the material document posted through physical inventory.

In an HU-managed storage location, Whenever a company receives stock from the vendor, the warehouse clerk receives the stock in HU's. They will deconsolidate the HU's into smaller HU's and then proceed with the quality inspection. To deconsolidate the received HU, the business will repack the HU received into smaller HU's through transaction HU02. To repack a HU, the storage type should allow repacking such storage types have no SU management, Capacity check, or Putaway strategy. If the HU lies in the Non repacking storage type, in this situation move the HU to repack storage type through transaction LT09 and then perform repacking.

Vendor master data is divided into three sections : General Data Purchasing Data Accounting Data Vendor master data is maintained by both purchasing and accounting departments in their respective purchasing and accounting sections. Purchasing data will be maintained at the Purchase Organisation level whereas accounting data will be maintained at the company code level. Data maintained at general data is client level ie., this data is common for both departments. Configuration Changes : Account group is a prerequisite to creating vendor master data. It controls the vendor type ie., one-time vendor or regular vendor. Account group controls number ranges, field status, and Partner schema. Number Ranges : Vendor number ranges can be maintained as Internal and External.  In the case of Internal number ranges, the system will propose the number at the time of vendor creation. For external number ranges, Vendor number is available for manual input. Number series will be managed by Number rang

Below are the options that can avoid that conditions update in the condition tab of the Purchase Order : Use T-code OMET to set function authorizations and define that the conditions cannot be changed.  Consider changing the condition type by using T-code M/06. If you set the indicator 'Manual Entries' to D, then it is not possible to change the condition in the purchase order.

Enterprise Structure Assignment  Relationship between individual org. elements are maintained here ********************************************************** Plant to company code assignment : Can we assign one plant to multiple company codes? One plant can be assigned only to one company code one company code can have multiple plants  ************************************************************ one plant can have 'N' number of storage locations ************************************************************ Purchase organization to company code assignment Can we assign one purchase org. to multiple company codes? One Purchase org. Cross company code purchases if I assign company code to purchase org. then I am restricting purchase org. to specific company code If I do not maintain any company code in the assignment then the purchase org. can be used for purchase goods for multiple company codes ************************************************************* Purchase organization to