Professional Documents
Culture Documents
1. Condition Table
SPRO/ Material Management/Purchasing/Message/ Output Control/Condition
Tables/Define Condition Table for Purchase Order
Select: Purchasing Doc. Type, Purchasing Organization, Vendor
2. Access Sequences
SPRO/ Material Management/Purchasing/ Message/Output Control/Access
Sequences/Define Condition Table for Purchase Order
3. Message Type
SPRO /Material Management/ Purchasing/ Message/ Output Control/Message
Types/Define Message Type for Purchase Order {NEU}
4. Message Determination Schemas
4.1. Message Determination Schemas
SPRO/ Material Management/Purchasing/ Message/ Output
Control/Message Schema/Define Message Schema for Purchase Order/ Maintain
Message Determination Schema
4.2. Assign Schema to Purchase Order
SPRO/ Material Management/Purchasing/Message/Output
Control/Message ne Message Schema for Purchase Order/Assign Schema to Purchase
Order
5. Partner Roles per Message Type
SPRO/Material Management/Purchasing/ Message /Output Control/Partner Roles per
Message Type/Define Partner Role for Purchase Order
6. Condition Record
SAP Menu/Logistics/Material Management/Purchasing/Master data/Messages/Purchase
Order/ MN04 (Create using medium EID Electronic Data Interchange ‘6’)
Significance of Message Output Type
In the created EDI (Electronic Data Interchange) output type of the purchase order, the
processing routine contains the program RSNASTED which is responsible for sending
the document to the Partner as an IDOC.
The Program RSNASTED is the processing program for each output type, which
depending on the definitions for the output mode maintained in the EDI partner profile,
will generate and write only one Intermediate Document to a file.
RSNASTED processes entries in the NAST table, which stores an entry for each output
record created from application document.
For the created PO, the IDOC created can be checked in IDOC List (WE02).
In case of issues in document transfer, this is the first place to be checked. Green status
indicates successful transfer of data from the ECC system.
Creating PO in MM
Once the PO has been released, this output message type triggers the IDoc
which takes the PO details to the SUS system.
SUS Portal
The vendor logs onto the SUS Portal using the User Id provided to them, to check the
PO, GR, Invoice notifications, to create ASN, Invoice uploading and to see Payment
details.
The PO details are sent as an outbound IDoc from the ECC system onto the XI/PI
system.
In the XI/PI system, this IDoc is mapped into an xml file and sent to the SUS system.
Thus, the PO details are visible to the Vendor in his SUS portal id.
The Vendor will be able to see all the Purchase Orders made against him by the
organization in this menu.
Here he can individually go and accept and view details of each of the purchase orders.
Current PO Status displays if it is a new PO or an already accepted/confirmed PO.
New POs are to be accepted by the Vendor, confirming that the terms of the PO
document are acceptable.
As seen in the screen shot below the Vendor is able to see the PO number, date,
company code, Company name and Terms of Payment in the General information layer.
The item code, details, quantity, rate, gross value and delivery date are visible in the
item Overview tab.
The fields in these tabs are customizable and the layout is modified as per business
requirement.
After accepting the PO the Vendor can then view and update the progress with respect
to this PO from the menu screen.
The acceptance of PO by the Vendor can be sent as a PO response to the ECC system
via XI/PI.
This is reflected in the PO Confirmations tab in Item detail in ECC.
Advanced Shipping Notice in Supplier Portal
Advanced Shipping Notification (ASN) is a notification that is sent by the vendor to the
organization when the goods are dispatched.
It generally includes information about the means of transport of the goods and
document reference against which it is created.
Here is an ASN screen in the SUS portal.
ASN is sent from the SUS to ECC system via the XI/PI system.
Once the goods are physically received at the storage location, Goods Reciept is done.
The details of the GR are required for the vendor to get a confirmation of delivery.
Preview of the Invoice uploaded. The Invoice details have to be entered manually at the
SAP ECC system in transaction MIRO. The uploaded Invoice is matched against MIGO
for invoice verification.
The Vendor can view Payments made to him in the SUS portal as shown below.
There can be multiple payments made to the Vendor against the same invoice or have a
single payment. This is based on the payment terms maintained against the vendor.
ERP, SAP MM sap materials management), sap mm. permalink.