Search This Blog...

Showing posts with label Info Record. Show all posts
Showing posts with label Info Record. Show all posts

Wednesday, November 16, 2016

Using Purchasing Contracts in SAP

By definition Contracts are long term agreements the business enters with the vendor for providing a certain quantity of a product for period of time. In SAP, this can be represented by a Purchasing Contract. Contracts can be created for the value or quantity. These contract can be set up to reduce or to be utilized by purchase orders that are being placed with reference to the contracts. Typically the businesses scenario for using Contracts would be when they want to reserve capacity at the vendor or for booking greige in the manufacturing context.

Happy Reading!!

Please feel free to post your suggestions, feedback and comments!

Author: Tharaka Perera


Wednesday, August 24, 2016

How to Set Up Basic Confirmations

Confirmation control in SAP is the mechanism of tracking the various stages of the procurement process from the time the purchase order is sent to the vendor, up until the goods receipt is done. 

The different stages could be PO receipt, order acknowledgement, Exfactory date communication, shipping notification etc. Depending on the business requirement the confirmation control in SAP can be set up in such a way that each of these stages can be tracked with a confirmation to the purchase order by defining them as a Confirmation Category. The grouping and sequencing of the Confirmation Categories is done in the setup of the Confirmation Control key.
Standard SAP provides a set of commonly used Confirmation Categories and Confirmation Control keys, allowing the flexibility to additional Confirmation Categories and Confirmation Control keys to be defined. In this document we will see how this can be achieved.


Happy Reading!!

Please feel free to post your suggestions, feedback and comments!

Author: Tharaka Perera

How to Set Up Basic Confirmations by Malith Tharaka Perera on Scribd

Wednesday, May 18, 2016

Inter company Stock Transport Order Processing

Companies with plants in multiple locations typically have the requirement to transfer stock between plants. The STO (stock transport order) process is used to handle this transfer systematically in SAP. 
However if these plants belong to different Company Codes then we need to use the Intercompany STO process. This requires several configuration steps and prerequisites to be in place for this solution to work and entities can benefit from the ability to monitor stock in transit, traceability through document flow and ability to account for delivery costs on the stock transport order.
In this document we will discuss the prerequisites and configuration that needs to be in place to achieve the Inter company Stock Transport Order process in SAP.
Please click here to read the invoice creation part of this process.
  • For Intra Company Stock Transport Order Processing, please click here.
  • For Rush Stock Transport Orders in SAP Fashion Management Solution (FMS) (Where delivery get created automatically at STO save), click here.
  • For stock transport orders between storage locations, please click here.
Happy Reading!!

Please feel free to post your suggestions, feedback and comments!

Author: Tharaka Perera

Friday, March 18, 2016

Purchasing Partner Determination

Businesses have to interact with different third party partners such as vendors, buying offices, invoicing parties etc. during the purchasing process. SAP provides functionality to define and clear identify the role and relationship of these parties to the supplier.

Happy Reading!!

Please feel free to post your suggestions, feedback and comments!

Sunday, February 28, 2016

Process Inbound IDOCs From PI using serialization

Sometime back we discussed about how we can process IDOCs using serialization in SAP. Click here to read it. 
There are business requirements where you need to process multiple IDOC message types in a serialized manner using PI immediately without a scheduled batch job. i.e. Customer master with address master (DEBMAS with ADRMAS) Vendor master with address master (CREMAS with ADRMAS) Info record master with vendor master & material master (INFREC with MATMAS and CREMAS) In order to process these IDOC’s successfully, you must process then in a sequence. It is not necessary IDOCs to be for master data distribution, you can serialize any message type. 

Happy Reading!!

Please feel free to post your suggestions, feedback and comments!

Author: Harsha Thelikorala

Saturday, January 30, 2016

Process Inbound IDOCs Using Serialization

When there is a dependency between IDOC message types while processing or distributing, IDOCs must be processed in a serialized manner. 

In order to achieve this requirement, IDOC serialization must be used.

i.e. Vendor Master, Customer Master, Material Master, etc.

If you want to read about how we can process Inbound IDOCs from PI Using Serialization; please click here.


Happy Reading!!

Please feel free to post your suggestions, feedback and comments!

Author: Harsha Thelikorala