SAP Logistics

 At times, business requires release strategy to be triggered for purchasing documents based on custom parameters or through internal validations. In this case, we cannot go through the standard release strategy due to custom validations or fields.  To accomplish this requirement, new logic need to be maintained in Customer exit: EXIT_SAPLEBND_002 .  Through this exit, we can perform changes to the communication structure.

There are two types of data in SAP : 1. Master data 2. Transaction data Master data : It is a kind of data that doesn't change regularly i.e., static in nature For example: if you require a bank account, we are required to fill some kind of application form where our personal details are given like name, email address, etc... this is called master data Transactional data : Master data is the basis for transactional data. Transactional data changes regularly. For example: based on the application bank account number is generated by the bank which will be used for performing transactions. Master Data : There are different types of master data in MM : 1. Vendor Master data 2. Material master data 3. Purchase info records 4. Source list 5. Quota arrangement 6. Service Master data... There are other master data as well like Output, conditions, etc which are used during transactional data processing Master data is created through an easy access screen and is non-transportable. It is requ

 At times, business users do purchase orders for the purchase requisitions created through sales orders. Again, after few days business users will try to use the same purchase requisitions to create new purchase orders.  In this situation, SAP throws the error message Error '06249' even though it is maintained as a warning message in system messages. This is standard SAP functionality and below is the workaround need be implemented as proposed by SAP in the note mentioned in the subject line.   The following workarounds are possible - from both MM and SD perspectives: Solution for MM side: Use the already existing PO + item. In this existing PO item, please create a new delivery schedule (tab "delivery schedule") for the new delivery date and the open units, then the system will allow you to continue. - or - Solution for SD side: Create a new schedule line in the old sales order item, or create a new item in the sales order for the remainin

 At times, businesses wish to send custom fields in the SAP to other partner systems. As these are Z fields, standard SAP doesn't push this data in partner systems. In this situation, Below are the actions to be done. 1. Enhance the IDoc type with a custom segment and add fields to it 2. Populate the values of the custom fields through exit: EXIT_SAPLVV01_001.

Enterprise structure is the term used for organizational structure in SAP. All the company organizational elements are mapped at the enterprise structure level. Below are the important elements of organizational structure from a Material Management (MM)  perspective : Purchase Organisation Purchasing group Plant Storage Location Purchase Organisation Purchase organization is the legal entity and is responsible for all kinds of purchase activities within an organization. Ideally, Purchasing department is a company that is represented as a purchase organization Purchasing Group Buyer or group of buyers in a company purchasing department are represented as a purchasing group in SAP Plant  A manufacturing entity of a company or depo or any location that involves some kind of activity in a place can be treated as a Plant in SAP Storage location it's a subdivision of a plant where the stock will be kept. Setting up of enterprise structure is done in two parts : 1. Definition 2. Assignmen

 At times, there is a a situation where the business requires a release strategy to be triggered if there are any changes to the purchase order document value either increase or decrease of document value. In general, standard SAP does trigger a release strategy if there is an increase in document value but however, if there is any decrease in the document value system doesn't trigger release strategy. This post covers the technical changes that we have to make to trigger release strategy if there is any decrease in the document value to that of the released amount. Release strategy at purchase order level is triggered based on the function module - 'ME_REL_STRATEGIE_EKKO' so we are required to make changes in this FM to accomplish this requirement. Perform reset is used to reset the release strategy post-release of the document. IF  cekko -gnetw  GT f1 .            PERFORM reset              USING e_frgst e_frggr                   e_frgzu e_frgkz e_frgrl .           e_

  At times, we will have a table and requires to find a transaction for it.  In this situation, use the table - 'TSTCP' and pass the table name *XXXX* in the parameter field. Then click on execute to display the transaction for the table.