(713) 479-7300 [email protected]

TRANSACTIONS

NLINK ADC TO SAP SOLUTION SAP BARCODING 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.

SAP Plant Maintenance / MRO

The SAP Plant Maintenance (PM) module handles planning and tracking of goods used for maintenance of technical objects (assets). Processing maintenance orders often requires tracking time confirmations by operations, adding material items to the order (with or without corresponding goods issue from inventory) and the ability to create new maintenance orders to support unplanned scenarios. An occasional need to update material inventory bin location on the material master has also proven useful to some of our customers.

SAP BARCODE TRANSACTIONS

The pre-configured Create Maintenance Orders transaction in the NLINK ADC to SAP Solution prompts the user for a technical object number (Equipment or Functional Location). The interface will validate the input technical object number, and based on a pre-defined set of defaults that is changeable by the user, the interface will create a maintenance order. Option to automatically release the order is available such that users can begin processing against the order.

The pre-configured Time Confirmation for Work Order transaction in the NLINK ADC to SAP Solution prompts the user for their personnel number and the work order number. The interface will validate the input information against SAP, and if valid, will display the work order operations for the user to select.

Once the operation is selected, users have the option of choosing ‘Start’ or ‘Complete’. When the user chooses ‘Start’, the solution will capture the current date/time for later processing. When the user chooses ‘Complete’, the solution will post the data to SAP for time confirmation against the input work order and operation (Transaction IW41). Option to edit the input times before posting to SAP is also available.

The pre-configured Add Components to Work Order transaction in the NLINK ADC to SAP Solution prompts the user for the order number, usually scanned off the order documentation. The NLINK ADC to SAP Solution validates the order number and, if valid, returns the order operation (to which the components will be assigned) on the displayed for users to select.

Once the operation is selected, the interface prompts the user to scan the material number(s) to be added to the order, along with the quantity. When the user selects the ‘Post’ button, the NLINK ADC to SAP Solution posts the material number(s) the SAP work order. Options to validate plant and storage location, as well as linking directly to MB1A-261 are also available.

The pre-configured Maintenance Notification Update transaction in the NLINK ADC to SAP Solution allows users to update an existing maintenance notification. The solution prompts the user to provide the notification number. If the scanned value is valid in SAP, the remaining input fields will be enabled for the user to add additional data. When the user chooses the ‘Post’ option, the solution will post the data to SAP to update the notification.

The pre-configured Goods Issue to Work Order transaction in the NLINK ADC to SAP Solution prompts the user for the Work Order number, usually scanned off the order documentation. The NLINK ADC to SAP Solution then returns the matching line item information for verification of quantity and issuing location. The user can navigate between items using the << and >> buttons. Finally, the NLINK ADC to SAP Solution posts the goods movement using Movement Type 261 to the SAP system and notifies the user of the success of the transaction. Option to link goods issue to Asset Serial Number is also available.

The pre-configured Goods Issue to Service Order transaction in the NLINK ADC to SAP Solution prompts the user for the Service Order number, usually scanned off a order documentation. The NLINK ADC to SAP Solution retrieves all matching and open reservation items associated with the service order. Each reservation item is shown one at a time. The user can navigate between items using the << and >> buttons. When the user posts an issue against a particular item, the NLINK ADC to SAP Solution will post the goods movement using Movement Type 921 to the SAP system and notifies the user of the success of the transaction.

The pre-configured Goods Issue Reversal to Work Order transaction in the NLINK ADC to SAP Solution prompts the user for the Work Order number, usually scanned off the order documentation or packaging. The NLINK ADC to SAP Solution then returns the matching line item information for verification. The user can navigate between items using the << and >> buttons. Finally, the NLINK ADC to SAP Solution posts the goods movement using Movement Type 262. to the SAP system and notifies the user of the success of the transaction. Option to link goods issue reversal to Asset Serial Number is also available.

The pre-configured ‘Set Bin Location’ transaction in the NLINK ADC to SAP Solution prompts the user for the material number, plant, and storage location. Based on the input data, the interface will validate and retrieve the current Storage Bin description in SAP. If user changes this value, the NLINK ADC to SAP Solution will update the storage bin data in the material master plant/SLOC Bin Location. The bin location will then be visible in the SAP inventory view.

SAP Purchasing / Goods Receipt

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.

SAP BARCODE TRANSACTIONS

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 / or 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.

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.

SAP Transfer Posting

SAP uses a Stock Transfer or a Transfer Posting to physically or logically move goods around internally, or to combine / reassign materials or material stock. 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.

SAP BARCODE TRANSACTIONS

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 Material to Material transaction in the NLINK ADC to SAP Solution uses the Movement Type 309 (Material to Material Transfer). It prompts the user for the issuing and receiving Material, source and destination Plant and Storage Location. 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.

The pre-configured Create TO for Bin to Bin Transfer transaction in the NLINK ADC to SAP Solution prompts the user for the Warehouse, Movement code, Plant, Storage Location and Batch or Material Number, usually scanned off documentation or packaging. The NLINK ADC to SAP Solution then prompts the user for the source and destination storage type, section and bin. Finally, the NLINK ADC to SAP Solution creates a Transfer Order (TO) in the SAP system and notifies the user of the success of the transaction.

The pre-configured Transfer Order (Picking) Confirmation transaction in the NLINK ADC to SAP Solution prompts the user for the Warehouse and Transfer Order (TO) number, usually scanned off documentation or packaging. The NLINK ADC to SAP Solution returns all matching and open (unconfirmed or partially confirmed) TO lines. Each TO line is shown one at a time. The user can navigate between TO lines using the << and >> buttons. The user marks all desired lines by checking the CONFIRM box for each line. Finally, the NLINK ADC to SAP Solution posts a confirmation containing all selected lines to the SAP system and notifies the user of the success of the transaction.

The pre-configured Transfer Order (Putaway) Confirmation transaction in the NLINK ADC to SAP Solution prompts the user for the Warehouse and Transfer Order (TO) number, usually scanned off documentation or packaging. The NLINK ADC to SAP Solution returns all matching and open (unconfirmed or partially confirmed) TO lines. Each TO line is shown one at a time. The user can navigate between TO lines using the << and >> buttons. The user marks all desired lines by checking the CONFIRM box for each line. Finally, the NLINK ADC to SAP Solution posts a confirmation containing all selected lines to the SAP system and notifies the user of the success of the transaction.

SAP Physical Inventory

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 following Physical Inventory transactions are currently available:

SAP BARCODE TRANSACTIONS

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 Recount transaction in the NLINK ADC to SAP Solution prompts for the Physical Inventory Document number. The NLINK ADC to SAP Solution then returns the document count data for verification and prompts for the new count 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 / Recount combo transaction in the NLINK ADC to SAP Solution prompts for the Material number. The NLINK ADC to SAP Solution then returns the current active physical inventory document data, and prompts for the count quantity. If the item has been counted, the count quantity will also be displayed for verification. When the user posts the count quantity, the NLINK ADC to SAP Solution automatically checks to determine of the post should be a count (MI04) or a recount (MI05) posting.

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.

SAP Production / Manufacturing Orders

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 may make 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.

SAP BARCODE TRANSACTIONS

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 number and / or 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.

The pre-configured Production Order Confirmation for Time Tickets in the NLINK ADC to SAP Solution prompts the user for the Production Order number and a specific operation, usually scanned off the order documentation or packaging. The NLINK ADC to SAP Solution then returns the matching line item information for verification, and prompts users for quantity to be confirmed. Finally, the NLINK ADC to SAP Solution posts the confirmation to the SAP system and notifies the user of the success of the transaction. The option to combo this transaction with MB1A-261 or MB31-101 exists if necessary.

The pre-configured Production Order Confirmation on Header Level in the NLINK ADC to SAP Solution prompts the user for the Production Order number, usually scanned off the order documentation or packaging. The NLINK ADC to SAP Solution then returns the matching order item information for verification, and prompts users for quantity to be confirmed. Finally, the NLINK ADC to SAP Solution posts the confirmation to the SAP system and notifies the user of the success of the transaction.

SAP Outbound Delivery

In SAP, an Outbound Delivery is a composition of the goods that is provided for shipping. The Outbound Delivery is the basis for the Advanced Shipping Notification (ASN) and Delivery Note that are sent to the product recipient. Outbound Deliveries can be applied to Sales Orders, Purchase Orders, or Stock Transport Orders. When you create an outbound delivery, you initiate shipping activities such as picking and transportation scheduling.

SAP BARCODE TRANSACTIONS

The pre-configured Create Outbound Delivery for Sales Order transaction in the NLINK ADC to SAP Solution prompts the user for the Sales Order number and a material availability date (defaulted to the current date, but editable). The NLINK ADC to SAP Solution verifies that an active outbound delivery document does not exist, then returns the matching line item information for verification. Finally, the NLINK ADC to SAP Solution posts the request to the SAP system and notifies the user of the success of the transaction. The option to combine this with the VL02N Transaction is also available.

The pre-configured Create Outbound Delivery for Stock Transport Order transaction in the NLINK ADC to SAP Solution prompts the user for the Stock Transport Order number. The NLINK ADC to SAP Solution verifies that an active outbound delivery document does not exist, then returns the matching line item information for verification. Finally, the NLINK ADC to SAP Solution posts the request to the SAP system and notifies the user of the success of the transaction. The option to combine this with the VL02N Transaction is also available.

The pre-configured Outbound Delivery Confirmation transaction in the NLINK ADC to SAP Solution prompts the user for the Outbound Delivery Document number OR the Sales Order / Stock Transport Order Number. The NLINK ADC to SAP Solution verifies that an active outbound delivery document exists, then returns the matching line item information for verification. After user enters the delivery quantity, the NLINK ADC to SAP Solution posts the request to the SAP system and notifies the user of the success of the transaction.

SAP Stock Inquiries

Inventory stock inquiries are sometimes necessary to reduce the likelihood for Goods Movement Errors. The following Stock inventory inquiry transactions are available:

SAP BARCODE TRANSACTIONS

The pre-configured Plant Stock per Material transaction in the NLINK ADC to SAP Solution prompts the user for the material number. The NLINK ADC to SAP Solution then returns the inventory for the material in SAP, and displays the results on the screen. Users have the option to filter the results displayed by plant, storage location, Batch, and/or non-zero values.

The pre-configured Bin Stock per Material transaction in the NLINK ADC to SAP Solution prompts the user for the Warehouse, Plant and Batch or Material Number, usually scanned off documentation or packaging. When the user selects the QUERY button, the NLINK ADC to SAP Solution returns all matching Warehouse Quants. Each Quant is shown one at a time. The user can navigate between Quants using the << and >> buttons. This is a reporting only transaction and does not include any posting to SAP.

SAP Fixed Assets

Many organizations face a significant challenge to track the location, quantity, condition, maintenance and depreciation status of their fixed assets. By tracking fixed assets using bar code tags for easy and accurate reading, companies can periodically take inventory with a mobile barcode reader and then produce a variety of reports. As a result, companies reduce expenses through loss prevention and improved equipment maintenance. They reduce new and unnecessary equipment purchases, and they can more accurately calculate taxes based on depreciation schedules. In general, Fixed Assets need to be created, edited, moved, verified and (ultimately) retired.

SAP FIXED ASSET BARCODE TRANSACTIONS

The pre-configured Create Fixed Asset transaction in the NLINK ADC to SAP Solution prompts the user for a Company Code, Asset number and, if necessary, an Asset Sub number. This transaction will first validate to see if the asset exists in SAP. If the asset exists, details for the asset will be displayed for users to edit. If the asset does not exist, the interface will create a new asset using data from a pre-defined asset as reference. After the asset is created, details of the created asset will be displayed for users to edit, with the input Asset Number – Sub number posted as the Inventory Number. Optional inputs to allow users to select the pre-defined reference asset number can also be supported.

The pre-configured Inventory Fixed Asset Transaction in the NLINK ADC to SAP Solution prompts the user for a Company Code, Asset number and, if necessary, an Asset Sub number. This transaction will validate that the asset exists in SAP, and if so, will display asset details for users to view. Upon posting, this transaction will update the asset Last Inventory Date, along with the Inventory note. Optional updates to other asset details data can also be supported as required.

The pre-configured Transfer Fixed Asset Transaction in the NLINK ADC to SAP Solution prompts the user for a Company Code, Asset number and, if necessary, an Asset Sub number. This transaction will validate that the asset exists in SAP, and if so, will display additional asset transfer details for users to enter. Upon posting, this transaction will post an intra-company asset transfer.

The pre-configured Transfer Fixed Asset Transaction in the NLINK ADC to SAP Solution prompts the user for the Source (original) Company Code, Asset number and, if necessary, an Asset Sub number. This transaction will validate that the asset exists in SAP in that company code, and if so, will display additional asset transfer details for users to enter. Upon posting, this transaction will post an inter-company asset transfer.

The pre-configured Retire Fixed Asset without Revenue transaction in the NLINK ADC to SAP Solution prompts the user for a Company Code, Asset number and, if necessary an Asset Sub number. This transaction will validate that the asset exists in SAP, and if so, will prompt the user for a short description as the reason for retirement. Upon posting, this transaction will default the current date as the asset value date for retirement. Optional updates to any of the asset data can also be supported as required.

The pre-configured Retire Fixed Asset with Revenue transaction in the NLINK ADC to SAP Solution prompts the user for a Company Code, Asset number and, if necessary an Asset Sub number. This transaction will validate that the asset exists in SAP, and if so, will prompt the user for the Revenue value, and a short description as the reason for retirement. Upon posting, this transaction will default the current date as the asset value date for retirement. Optional updates to any of the asset data can also be supported as required.

The pre-configured Block Fixed Asset transaction in the NLINK ADC to SAP Solution prompts the user for a Company Code, Asset number and, if necessary, an Asset Sub number. This transaction will validate that the asset exists in SAP. Upon posting, this transaction will set the asset status to block (or Lock).Note: A block status on the asset keeps the asset values from changing for end-of-period depreciation calculations. Asset transfers and retirement postings are still possible. This is typically used when an asset is to be sold, or to prevent future postings to an asset under construction once the project is complete.

The pre-configured Delete Fixed Asset transaction in the NLINK ADC to SAP Solution prompts the user for a Company Code, Asset number and, if necessary, an Asset Sub number. This transaction will validate that the asset exists in SAP. Upon posting, this transaction will delete the Fixed Asset from the system.Note: Deleting assets is sometimes necessary to remove old assets (legacy assets from previous systems) after an Asset Transfer transaction. Fixed Assets can only be deleted when no postings have been made.

SAP FIXED ASSET BARCODE REPORTS

The pre-configured Download Fixed Asset Inventory List transaction in the NLINK ADC to SAP Solution prompts the user for a Company Code and fiscal year. This transaction will retrieve the list of Fixed Assets in SAP with the setting for “include asset in inventory list” set to TRUE. The NLINK ADC to SAP Solution for Fixed Assets then retrieves a list of Fixed Assets that fit the entered criteria. The list will be displayed for the users to view, along with an option to email, or to output locally to a delimited format file. Additional optional filter parameters are available to further limit this list.

The pre-configured Missing Fixed Asset Inventory List Transaction in the NLINK ADC to SAP Solution prompts the user for a Company Code and a fiscal year. This transaction will retrieve the list of Fixed Assets in SAP which have not been inventoried. This list will be displayed for users to view, along with an option to email, or to output locally to a delimited format file.

The pre-configured Inventoried Fixed Asset Inventory List Transaction in the NLINK ADC to SAP Solution prompts the user for a Company Code and a fiscal year. This transaction will retrieve the list of Fixed Assets in SAP which have been inventoried as of the current date. This list will be displayed for users to view, along with an option to email, or to output locally to a delimited format file.

The pre-configured Blocked Fixed Asset Inventory List transaction in the NLINK ADC to SAP Solution prompts the user for a Company Code and fiscal year. This transaction will retrieve the list of Fixed Assets in SAP with Acquisition Lock flag set to TRUE. The list will be displayed for the users to view, along with an option to email, or to output locally to a delimited format file. Additional optional filter parameters are available to further limit this list.

The pre-configured Retired Fixed Asset Inventory List transaction in the NLINK ADC to SAP Solution prompts the user for a Company Code and a fiscal year. This transaction will retrieve the list of Fixed Assets in SAP with Last Retirement Date within the input fiscal year. The list will be displayed for the users to view, along with an option to email, or to output locally to a delimited format file. Additional optional filter parameters are available to further limit this list.

The pre-configured Retire Fixed Asset with Revenue transaction in the NLINK ADC to SAP Solution prompts the user for a Company Code, Asset number and, if necessary an Asset Sub number. This transaction will validate that the asset exists in SAP, and if so, will prompt the user for the Revenue value, and a short description as the reason for retirement. Upon posting, this transaction will default the current date as the asset value date for retirement. Optional updates to any of the asset data can also be supported as required.

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.

CASE
STUDIES

At Junot, success means providing our customers with world-class SAP integration solutions. Here are some real-world NLINK ADC to SAP Solution deployments which highlight how working with Junot Systems has benefited just one small cross-section of our customers.

PRODUCT
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 contact us today and we will be glad to arrange it.

TECHNICAL
INFORMATION

For more technical and product information regarding the NLINK ADC to SAP Solution please contact: [email protected]

SALES INFORMATION

For sales and pricing information regarding the NLINK ADC to SAP
Solution please contact: [email protected]