Faster, Cheaper Better SAP Integration
 
 
 Company
 
 Solution
 
 Transactions
 
 Partners
 
 Certifications
 
 Compatibility
 
 Support
 
 Contact
 
 




           

Simple, Affordable, Low-Risk ADC to SAP Solutions

NLINK ADC TO SAP SOLUTION SAP TRANSACTIONS

The NLINK® ADC to SAP Solution comes with a rich set of pre-built SAP Automatic Data Collection transactions. Determining which of these transactions are the most appropriate for your particular situation depends on a number of factors, including your project's functional requirements and which modules of SAP you use. The information presented here will help you make an informed decision.

Goods Receipt for Purchase Order (MB01)
Using the Goods Receipt for Purchase Order transaction makes sense if the SAP installation includes the Purchasing component of the MM (Materials Management) module, which handles purchases of goods from vendors. The Purchase Order in the SAP system includes information such as the vendor and the quantities and types of goods purchased. When a delivery arrives, the recipient should verify the contents of the delivery against the original Purchase Order document. Using the Goods Receipt for Purchase Order transaction allows the SAP system to update the purchase order history, valuate the goods receipt, and verify vendor invoices.

The pre-configured Goods Receipt for Purchase Order transaction in the NLINK ADC to SAP Solution prompts the user for the Purchase Order number and a material or batch number, usually scanned off the delivery documentation or packaging. The NLINK ADC to SAP Solution then returns the matching line item information for verification of quantity and receiving location. Finally, the NLINK ADC to SAP Solution posts the goods movement using Movement Type 101 (Receipt to Warehouse/Stores) to the SAP system and notifies the user of the success of the transaction.


Goods Receipt without Purchase Order (MB1C)
If the SAP installation does not include the Purchasing component of the MM (Materials Management) module, it makes sense to use the Goods Receipt without Purchase order transaction to accept delivery of external goods into inventory.

The pre-configured Goods Receipt without Purchase Order transaction in the NLINK ADC to SAP Solution prompts the user for the material number, usually scanned off the delivery documentation or packaging. The NLINK ADC to SAP Solution then returns the material information for verification and prompts for the quantity and receiving location. Finally, the NLINK ADC to SAP Solution posts the goods movement using Movement Type 501 (Receipt without Purchase Order into Warehouse) to the SAP system and notifies the user of the success of the transaction.


Goods Receipt for Production Order (MB31)
Goods Issue to Production Order (MB1A)
If the SAP installation includes the Production Order component of the PP (Production Planning) module, which handles planning and tracking of goods used for in-house production of materials, then using the Goods Receipt for Production Order and Goods Issue to Production Order transactions makes sense. The Production Order in the SAP system includes information such as the material being produced, the quantities and types of goods needed to produce the material, and the destination of the finished material. The Goods Issue transaction tracks consumption of the goods needed to produce another material, while the Goods Receipt acknowledges the new material created as a result of completing the Production Order.

The pre-configured Goods Issue to Production Order transaction in the NLINK ADC to SAP Solution prompts the user for the Production Order number and a material or batch number, usually scanned off the production documentation or packaging. The NLINK ADC to SAP Solution then returns the matching line item information for verification of quantity and issuing location. Finally, the NLINK ADC to SAP Solution posts the goods movement using Movement Type 261 (Consumption for Order from Warehouse) to the SAP system and notifies the user of the success of the transaction.

The pre-configured Goods Receipt for Production Order transaction in the NLINK ADC to SAP Solution prompts the user for the Production Order and a material or batch number, usually scanned off the production documentation or packaging. NLINK then returns the matching order information for verification of quantity and receiving location. Finally, the NLINK ADC to SAP Solution posts the goods movement using Movement Type 101 (Receipt for Order to Warehouse) to the SAP system and notifies the user of the success of the transaction.


Goods Issue to Cost Center (MB1A)
The Goods Issue to Cost Center allows internal staging of goods for purposes other than production or sales. SAP will handle the account assignment changes based on the data provided.

The pre-configured Goods Issue to Cost Center transaction in the NLINK ADC to SAP Solution prompts the user for the issuing storage location and material number. The NLINK ADC to SAP Solution then returns the matching material information for verification and prompts for the quantity to remove and the receiving Cost Center code. Finally, the NLINK ADC to SAP Solution posts the goods movement using Movement Type 201 (Consumption for Cost Center from Warehouse) to the SAP system and notifies the user of the success of the transaction.


Goods Issue to Sales Order (MB1A)
If the SAP installation includes the SD (Sales & Distribution) module, then it handles withdrawal, picking and shipping of goods to customers. To post goods movements out to customers without the SD module, use the Goods Issue to Sales Order transaction.

The pre-configured Goods Issue to Sales Order transaction in the NLINK ADC to SAP Solution prompts the user for the issuing storage location and material number. The NLINK ADC to SAP Solution then returns the matching material information for verification and prompts for the quantity to remove and the external Sales Order number. Finally, the NLINK ADC to SAP Solution posts the goods movement using Movement Type 231 (Consumption for Sales Order from Warehouse) to the SAP system and notifies the user of the success of the transaction.


Transfer Posting Plant to Plant (MB1B)
Transfer Posting Storage Location to Storage Location (MB1B)
SAP uses a Stock Transfer or a Transfer Posting to physically or logically move goods around internally. Technically, the term Stock Transfer refers to a physical goods movement, while Transfer Posting refers to a logical goods movement. In practice, most people do not adhere to the distinction between the terms and use them interchangeably. The SAP system takes care of creating material and accounting documents as necessary, depending on the Movement Type and provided data.

The pre-configured Transfer Posting Plant to Plant transaction in the NLINK ADC to SAP Solution uses the Movement Type 301 (One-Step Transfer Posting Plant to Plant). It prompts the user for the issuing Plant, Storage Location and a material number or batch number. The NLINK ADC to SAP Solution then returns the existing inventory information for verification and prompts for the receiving Plant, Storage Location and quantity to move. Finally, the NLINK ADC to SAP Solution posts the goods movement to the SAP system and notifies the user of the success of the transaction.

The pre-configured Transfer Posting Storage Location to Storage Location transaction in the NLINK ADC to SAP Solution uses the Movement Type 311 (One-Step Transfer Posting Storage Location to Storage Location). It prompts the user for the issuing Storage Location and a material number or batch number. The NLINK ADC to SAP Solution then returns the existing inventory information for verification and prompts for the receiving Storage Location and quantity to move. Finally, the NLINK ADC to SAP Solution posts the goods movement to the SAP system and notifies the user of the success of the transaction.


Physical Inventory Count (MI04)
Physical Inventory Count without Reference (MI09)
Companies take Physical Inventories to reconcile the book quantities and values with the actual on-hand quantities and values of their stored goods. In SAP, you can use periodic, continuous, cycle counting or sampling procedures to generate the Physical Inventory documents, which indicate the materials and locations to count.

The pre-configured Physical Inventory Count transaction in the NLINK ADC to SAP Solution prompts for the Physical Inventory Document number. The NLINK ADC to SAP Solution then returns the storage location and material number for verification and prompts for the counted quantity. Finally, the NLINK ADC to SAP Solution posts the inventory count to the SAP system and notifies the user of the success of the transaction.

The pre-configured Physical Inventory Count without Reference transaction in the NLINK ADC to SAP Solution prompts for the storage location and material number. The NLINK ADC to SAP Solution then returns the material information for verification and prompts for the counted quantity. Finally, the NLINK ADC to SAP Solution creates the Physical Inventory document in the SAP system along with the inventory count and notifies the user of the success of the transaction.





VIDEO PRESENTATIONS

There`s really only so much information you can absorb by reading about an enterprise software product like the NLINK ADC to SAP Solution. At some point you need to see the software in action and that`s what the NLINK ADC to SAP Solution Video Presentations are all about.

REQUEST AN NLINK ADC TO SAP DEMO

If you have already seen the Video Presentations and would like to learn more by scheduling a WebEx demonstration of the NLINK ADC to SAP Solution, please click here.


TECHNICAL INFORMATION
For more technical and product information regarding the NLINK ADC to SAP Solution please contact .

SALES AND PRICING INFORMATION
For sales and pricing information regarding the NLINK ADC to SAP Solution please contact .






Copyright © 1997 - 2008, Junot Systems, Inc. | Privacy Policy | Terms of Usage
sales@adc-to-sap.com | 713.479.7300 | Contact