Toolkit for SAP consultants

What if we need to separate it for the special processes? What are the categories available? Do we really need a material number to create a Purchasing Information Record? What is the T-code to create and change PIR? Mass update Additional information  Conversion factors  How can purchasing info records be transferred via ALE? The 'Minimum Qty'  1900107 - MRP : Planned delivery time is taken from material master rather than info record 2892806 - The net prices/effective price are not updated in the info record after run the report RM06INP0 EINA-MATKL 2342644 - Updating tax code in info record according to InfoUpdate flag in PO 2657807 - Purchasing info record price history shows PO effective price rather than net price 2559559 - Info record not filled in STO Order unit 430543 - FAQ: Purchasing info record What is Purchasing Information Record? The relationships between vendors and their materials.  A vendor might have specific terms and conditions of purchase for a material.

Material master  EAN/ UPC/ and others Product hierarchy  Batch input programs for master data load/change Service master Service master record Model service specification Standard Service Catalog Material master  Product hierarchy  The material master, you can enter the hierarchical classification of the product. This is very useful in pricing and statistical analysis. The hierarchy is broken down into different levels. Each level signifies a certain characteristic of the product. Maintaining a product hierarchy The Product Hierarchy field appears in the material master view Sales: Sales Org 2. To maintain the value, use transaction code MM01 (Create Mode)or MM02 (Change Mode). Based on the structure of your product line, you can create your own product hierarchy. The standard SAP system offers a three-tiered product hierarchy. Level 1 and level 2 are five digits each. Level 3 is eight digits long (and is called the 5/5/8 schema). Thus, the total length of hierarchy adds up to 18

Basics Management of the Supply Chain Supply chain business processes Mapping Business Functions of a Company in the SAP System Procurement Process Area Operational Procurement Receiving and processing of quotations from vendors in response to an RFQ Creating and processing purchase requisitions  Creating and processing purchase orders Reference  Blocking a Purchase Order Line Item Automatically Create POs from Purchase Requisitions Progress Tracking Contracts Management Outline Purchase Agreements External Services Management Special Procurement Types Direct Procurement (51) Stock Transfers (Interplant Transfers; 40) Withdrawals from an Alternative Plant (70) Subcontracting (30) Consignment (10) Returnable Transport Packaging Pipeline Material Managed special stocks Sales Order Stock Project Stock Simplified Sourcing Material Requirements Planning Forecasting Inventory Management Physical Inventory Invoice and Payables Management Inventory Valuation and Account Assignment Early War

Version management  Usage of Revision Level for PP Masters -BOM and Routing ( Update: 07.09.2021 ) Objects Change master Change record Engineering record  ECM is used to change various fronts of production basic data (BOMs, task lists, materials, and documents ) with history (with date effectivity) or depending on specific conditions (with parameter effectivity). Version management  In the SAP system, we can make changes to objects both with and without history. Changes without history: When we change and save data, the old data is overwritten. We can only recall the data that saved last.  Changes with history: Document changes with Engineering Change Management. In the case of specific change objects (such as a material, document, or bill of material), Engineering Change Management can be used separately for each object.  How to use versions for a material master or a document?  Steps Create a change object and assign it to a material or document(transaction code CC01); Add changes

Changes to master data objects are managed using the Shared Master Data (SMD) tool. The SMD tool distributes master data changes to the decentralized systems. An important note is that the SMD tool is connected to the change document interface ( CDHDR and CDPOS ). If the master data changes are to be distributed, the application writes a change document. Configuration and use Activate the functionality for the change pointers? (Transaction BD61); Activate change pointers for this message type? (Transaction BD50); Activate Change Pointer per change doc it (Transaction BD52); Deactivate the change pointer with the Reduction tool (transaction BD53); SAP Note 'Reducing the amount of data for change pointers' (0420562), Are there still too many change pointers to be processed? The change pointers are analyzed with the transaction BD21 or the report RBDMIDOC in ALE and flagged as processed. If the change pointers are created periodically, this report should also run p

Designing a Report Interface using ALV SALV functions Normal ALV Table Display Adding Default PF STATUS in ALV Adding Custom PF STATUS in ALV Setting up Layout Add Header (Top of page) & Footer (End of Page) Changing Column settings Apply Colors Add & Handle Hotspot Apply Aggregations Apply Styles to Cell Apply sorts ICONs and Tooltips Columns Specific Grouping SALV Hierarchical Table Simple table display Adding Default PF Status Add Expand/Collapse Option IDA Display Sales Order Details Apply Filtering Set the parameter Example CL_ALV (old) Edit mode CL_SALV_HIERSEQ_TABLE Links Designing a Report Interface using SALV/IDA SALV (easy to implement if we do not need CDS views) , IDA (optimized for HANA), ALV Classic ( editable; simple, hierarchy ). Decide on the source Decide on the look ALV splitter  List fields  List functions Variant Layout Format ( colors ) Field descriptions Sorting Filtering Status with own buttons Editabale fields Events hotspot on field double click Toolb