SAP Logistics

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

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

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

At times, business requires to have new fields in the report output of transaction code ME1P which are not currently provided in the standard SAP report layout. In this situation, we have to go for enhancement. Below is the sample case to display the material description field in the report output. The material description is not provided in the standard SAP layout of ME1P. As this is not given in the standard SAP,  we have to follow the below process to display it. Add the new field in the structure  MEREP_OUTTAB_PRHIS. Then implement the BADI - ME_CHANGE_OUTTAB_CUS can be used for all enhancement of ALV reports.  Use method  IF_EX_ME_CHANGE_OUTTAB_CUS~FILL_OUTTAB to write the logic to display the desired output.