Solution ID: 200782287
Date Last Revised: 01/03/2005
Title: Inbound 852 (R47121)
Abstract: This paper documents the Inbound 852 (R47121) Product Activity data set.
Table of Contents
What is the Inbound 852?
Menu/UBE/Tables
Working with Product Activity Codes
Process for Receiving Product Activity Data
Example of an Inventory Adjustment
Example of an Inventory Transfer
What is the Inbound 852?
The Inbound 852 (R47121) is a Product Activity Data transaction set, used to report
inventory activity (transfers, adjustments, issues, cycle counts).
Note: The PeopleSoft EnterpriseOne Inventory Management , Sales Order Management
and Procurement systems must be used to receive product activity data.
The receiver of the transaction typically maintains inventory levels on their computer for
the sender of the transaction and plans when orders should be issued to replenish the
sender's stock.
Note: Currently, no Outbound 852 transaction set exists, only Inbound. Enhancement
SAR 5256620 requests this functionality.
Back to Top
Menu/UBE/Tables



The Inbound 852 transaction set is on menu G47241.
The UBE used is the EDI Product Activity Data Extraction (R47121).
The tables used for the transaction are the EDI Product Activity Data Header Inbound (F47121) and EDI Product Activity Data Detail - Inbound (F47122).


The EDI Product Activity Data Extraction (R47121) pulls information from the
47 tables and populates the Item Location (F41021), Item History (F4115), Item
Ledger (F4111) and Account Ledger (F0911) tables.
EDI Product Activity Data Inquiry - Inbound (P47120) is the Status
Inquiry/Revisions program for this process. Records can be added, revised and
reviewed here before running the EDI Product Activity Data Extraction (R47121)
UBE.
Back to Top
Working with Product Activity Codes
47/PA UDC Table: The codes in this UDC table specify the type of transaction and how
it affects inventory. The Description 02 field designates the activity.
- (Decreases Inventory): If the product activity code description 02 is '-', the transaction
functions similarly to the Inventory Issues (P4112) program. The quantity of the
transaction decreases the quantity on hand for Item Location (F41021) records and
updates the Item History (F4115) table if specified in the processing options. The
transaction also generates the necessary general ledger transactions to account for the
decrease if the item's General Ledger Code and Document Type interface with inventory.
+ (Increases Inventory): If the product activity code description 02 is '+', the transaction
functions similarly to the Inventory Adjustments (P4114) program. The quantity of the
transaction increases in the Item Location (F41021) record's quantity on hand. The
system writes the new quantity on hand to the Item Ledger (F4111) and generates the
necessary general ledger transaction to account for the receipt of the inventory.
I (Information Only): If the product activity code description 02 is 'I', the transactions
are informational only and do not update any EnterpriseOne table. The transaction is
edited for validity and prints on the Product Activity Audit Report.
R (Replaces Inventory On-Hand balance): If the product activity code description 02 is
'R', the transaction functions similarly to the Cycle Count Update (R41413)
program. The quantity of the transaction replaces the quantity on hand for the Item
Location (F41021) records. The system writes the new quantity on hand to the Item
Ledger (F4111), updates the Item History (F4115) table, and generates the necessary
general ledger transactions to account for the adjustment to the inventory.
T (Transfers Inventory from one Location to another): If the product activity code
description 02 is 'T', the transaction functions similarly to the Inventory Transfer (P4113)
program. The quantity of the first transfer transaction (the From Side) decreases the
quantity on hand for the Item Location (F41021) record. The second transfer transaction
(the To Side) increases the quantity on hand for the Item Location (F41021) record
(requires two records to be sent in). The transactions also generate the necessary general
ledger transactions to account for the changes to the inventory if the item's General
Ledger Code and the Document Type affect inventory.
Note: The Sort Selection Sequence field in the inbound detail record controls the order in
which transactions are processed. For example, process the beginning balances first, the
plus (+) transactions, then minus (-), and ending balances.
47/TH UDC Table: The codes in this UDC table specify how the Inbound Edit/Update
program for product activity data should process. Note: This functionality is
for FUTURE USE, but is a REQUIRED field.
Back to Top
Process for Receiving Product Activity Data
Populate the EnterpriseOne interface tables, EDI Product Activity Data Header Inbound ( F47121) and EDI Product Activity Data Detail - Inbound (F47122).



The external system sends the data to the EnterpriseOne interface tales, which
holds the data before it is copied to the application tables.
The external system is responsible for conforming to the format and other
requirements for the interface tables.
If the external system cannot write the information in the required format, it can
write the data to a flat file, and the inbound flat file conversion program will
convert the data to the required format.
After successfully processing the interface tables, run the EDI Product Activity Data
Edit/Create (R47121) program in proof or final mode.
The EDI Product Activity Data Inquiry - Inbound (P47120) program allows the user to
interactively review and revise the incorrect data.
After successfully processing the Inbound 852, the EDI tables will be updated as
Processed (EDSP = Y). These tables can then be purged/archived by using the EDI
Product Activity Data Inbound Purge (R47128A) program.
Back to Top
Example of an Inventory Adjustment:
Summary Availability (P41202) for Item before Issue is done.
The THCD field in the EDI Product Activity Data Header - Inbound (F47121) file must
be populated with a valid value from the 47/TH UDC table even though it is for
FUTURE use.
EDI Product Activity Data Detail - Inbound (F47122) required fields. The PACD field
uses a value from the 47/PA UDC table and controls how the transaction affects
inventory.
Processing Options for the EDI Product Activity Data Edit/Create (R47121) program.
Data Selection for the EDI Product Activity Data Edit/Create (R47121) program.
Note: A blank PDF is displayed.
Inquire on the EDI Document Number in EDI Product Activity Data Inquiry - Inbound
(P47120), to see that a Document Number was generated.
Summary Availability (P41202) has changed.
The transaction can be seen in the Inventory Adjustments (P4114) program.
Back to Top
Example of an Inventory Transfer
When working with transfers, all information is the same as the Inventory Issue, except
for the from and to locations.
Summary Availability (P41202) for Item in Branch Plant 30.
Summary Availability (P41202) for Item in Branch Plant 10.
Required Fields for EDI Product Activity Data Header - Inbound (F47121).
Required Fields for EDI Product Activity Data Detail - Inbound (F47122).
Description 02 in the 47/PA UDC Table for IT is 'T' for Transfer.
The definition of F T (FRTO) field.
The Processing Options and Data Selection for the EDI Product Activity Data Edit/Create
(R47121) program is the same as the first example and a blank PDF is generated as well.
EDI Product Activity Data Detail - Inbound (F47122) after running EDI Product Activity
Data Edit/Create (R47121) will show that the Document Number is generated.
On-Hand quantity has changed for Branch Plant 10 and 30 as seen in the Summary
Availability (P41202).
The document can be viewed in the Inventory Transfers (P4113) program.
Note: If using lots, be sure to populate the Lot Expiration Date, to eliminate date errors.
Back to Top