SAP-HANA
SLT (SAP Landscape Transformation Replication Server) in SAP HANA
What is SLT (SAP Landscape Transformation Replication)? SLT is the an ETL tool that allows you to...
Releasing a purchasing document means approving it. For this, our MM consultant can create release procedures to be used. There is a vast number of options that can be used for controlling the release of the documents.
Important information to know is that a purchasing document cannot be changed after it is released. That means that only the final version should be released. Unreleased documents (RFQ – request for quotation, PO – purchase order, scheduling agreement, contract) cannot be processed further (convert RFQ to quotation, PO to goods receipt, invoice verification). Process flow:
We can have a lot of different strategies for different situations. For example, you can define a release strategy that is dependent on document type, you can define a release strategy based on the purchasing organization, purchasing group, or any other crucial information for a purchasing document.
In most of the cases, one of the most used release strategy is based on the value of the purchase document.
Step 1) Lets define a release strategy such that will only request a manual release for purchasing documents with value greater than 100 Eur. For example if we have a PO of the value of 50 Eur, it will be autoreleased (will not require a release to be processed further). A purchase order for more than 100 Eur would require a release.
For this, in the background, there needs to be specified a characteristic.
Step 2) Assigning fields to a characteristic on the additional data tab. We are assigning field CEKKO-GNETW to the characteristic, because that field is a purchase document value.
Step 3) There also needs to be specified a class that holds the characteristic.
Step 4) Assigning a characteristic to a class. Afterwards, we can assign NETVALUE to a class called REL_PUR.
Step 5) Following steps need to be done in customizing.
Afterwards, your strategy is set and ready for live system tryout.
Step 6) We can see that our purchase order is created to a value of more than 100 Eur. If we create a PO for less than 100 Eur, it will be autoreleased.
Now we have a purchase order that needs to be released (approved) to be valid for further processing.
For the actual release of the purchasing document, we can use t-code ME28.
Step 1)
Step 2) On the next screen, we can see the purchase orders selected by our criteria.
Status of the purchase order has changed to released.
Step 3) You can see in the ME23N or ME22N transaction that our purchase order has altered statuses. "Release completed" and "Released" statuses are now shown in the PO header data.
Process flow is the same for all of the purchase documents (RFQ, PR, quotation etc).
Step 1) Purchasing document release has to be reversed in order for already released document to be changed.
Step 2) You will see the list of purchase documents available for release cancelation.
Cancelling a release isn't possible if your release strategy doesn't allow the release to be reversed. This is a setting maintained on the release indicator and release strategy level.
You can test a release strategy used by the purchasing document by clicking the "Release Strategy" button on the above screen. You can also simulate the strategy output with Simulate release button.
What is SLT (SAP Landscape Transformation Replication)? SLT is the an ETL tool that allows you to...
What is a Support Package? When an end user of SAP finds a bug in the SAP product, he reports the...
Define Access Sequence To define and maintain access sequences, you need to follow a few simple...
What is a Return? Return is where a customer is not satisfied with the product or the deliverable, &...
There are two types of goods movement against production order which impacts the inventory of the...
Step 1) Go to transaction code RSA1 to go to the Data Warehouse Workbench. Click the OK button....