Setting Up Manual Data for the eProcurement Integration
This chapter discusses how to:
Set up manual data for the eProcurement integration.
Load master data for the eProcurement integration.
Set up cross-references for the eProcurement integration.
Setting Up Manual Data for the eProcurement Integration
Due to their static nature, certain entities must be manually synchronized between the PeopleSoft Enterprise system and the JD Edwards EnterpriseOne system.
You must load the values for these JD Edwards EnterpriseOne codes into the PeopleSoft Enterprise system before you run the integration:
|
PeopleSoft Enterprise Entity |
JD Edwards EnterpriseOne Entity |
PeopleSoft Enterprise Navigation |
JD Edwards EnterpriseOne Navigation |
Comments |
|
Business Unit |
Branch/Plant |
eProcurement, Administer Procurement, Maintain Business Units, Purchasing Definition, Business Unit Definition |
Procurement System Setup (G43A41), Branch/Plant Constants |
We recommend that you manually enter the JD Edwards EnterpriseOne business unit (MCU) value for the branch/plant as the description of the branch/plant in the PeopleSoft Enterprise system. Entering the JD Edwards EnterpriseOne business unit number in the PeopleSoft Enterprise system makes it easier to looking up corresponding branch/plants in the two systems. |
|
Buyer |
Employees |
eProcurement, Administer Procurement, Maintain Procurement Users, Buyers |
Daily Processing (G0110), Address Book Revisions The search type is E. |
In the JD Edwards EnterpriseOne system, add address book records for employees using search type E. The User Profile/Address Book Batch Load adds the data to PeopleSoft Enterprise requesters. You must set up buyers manually in the PeopleSoft Enterprise system after the batch load is run. |
|
Country |
Country |
Set Up Financials/Supply Chain, Common Definitions, Location, Country |
UDC 00/CN |
The default in the PeopleSoft Enterprise system is a three-digit value; two-digit values need to be set up to match the length allowed in the JD Edwards EnterpriseOne system. A blank value in JD Edwards EnterpriseOne user-defined codes is invalid when running this integration. |
|
Currency Code |
Currency Code |
Set Up Financials/Supply Chain, Common Definitions, Currency, Currency Code |
Multi-Currency Setup (G1141), Designate Currency Codes |
A blank value in the JD Edwards EnterpriseOne system is invalid when running this integration. |
|
Currency Exchange Rates |
Currency Exchange Rates |
Set Up Financials/Supply Chain, Common Definitions, Market Rates, Market Rates |
Multi-Currency Setup (G1141), Currency Exchange Rate Entry |
The JD Edwards EnterpriseOne system is the system of record for exchange rates. Exchange rates should be set up the same in both systems, but the exchange rate from the JD Edwards EnterpriseOne system is used when the purchase order is paid. |
|
Freight Terms |
Freight Handling Codes |
Set Up Financials/Supply Chain, Common Definitions, Shipping and Receiving, Freight Terms |
UDC 42/FR |
|
|
Item Category |
Item Master Commodity Class Codes |
Items, Define Controls, Item Categories |
Inventory Master Transactions (G4111), Item Master Select Category Codes, Commodity Class from the Row menu. Use UDC 41/P1 to set up valid commodity classes. |
The PeopleSoft Enterprise system has both a Category ID and a Category Name. The Category ID is assigned by next numbers. You should enter Category Names in the PeopleSoft Enterprise system that match the Commodity Class Codes in UDC 41/P1 in the JD Edwards EnterpriseOne system. |
|
Payment Terms |
Payment Terms |
Set Up Financials/Supply Chain, Product Related, Procurement Options, Payments, Payment Terms - Single Payment |
Payment Terms Revisions (G00141), Payment Terms Revisions |
This integration supports simple payment terms only. The default in the PeopleSoft Enterprise system is a five-digit value; three-digit values need to be set up to match the length allowed in the JD Edwards EnterpriseOne system. |
|
Ship Via Codes |
Modes of Transport |
Set Up Financials/Supply Chain, Common Definitions, Shipping and Receiving, Ship Via Codes |
UDC 00/TM |
|
|
State |
State |
Set Up Financials/Supply Chain, Common Definitions, Location, State |
UDC 00/S |
The default in the PeopleSoft Enterprise system is a six-digit value. However, state codes must not exceed two-digits to match the length allowed in the JD Edwards EnterpriseOne system. State codes in the PeopleSoft Enterprise system have an associated two-digit country code. |
|
Tax Codes Tax Authority VAT Intrastat Tax Code VAT Intrastat Tax Authority |
Tax Rate Areas Tax Explanation Codes Tax Authorities |
|
|
Taxes are calculated in the PeopleSoft Enterprise system at the time of purchase order creation in the PeopleSoft Enterprise system, but the tax calculated by the JD Edwards EnterpriseOne system takes precedence over any tax calculated in the PeopleSoft Enterprise system because payment takes place in the JD Edwards EnterpriseOne system. |
|
Quantity Received Tolerance % |
Quantity Tolerance % |
Items, Define Controls, Item Categories, Category Definition 2 tab, Receiving Controls Note. Use this navigation to set receipt tolerance for an entire category. You can also set tolerance at the individual item level. |
Procurement System Setup (G43A41), Tolerance Rules |
The PeopleSoft Enterprise system supports tolerance on quantity only, not on amount. You must set up corresponding tolerance percentage for quantity to prevent a receipt that is created in one system from failing to be created in another system because it exceeds tolerance. |
|
Unit of Measure |
Unit of Measure |
Set Up Financials/Supply Chain, Common Definitions, Units of Measure, Units of Measure |
UDC 00/UM |
Dual unit of measure transactions are not supported for this integration. The default in the PeopleSoft Enterprise system is a three-digit value; two-digit values need to be set up. |
|
Vendor Roles |
Supplier |
|
Daily Processing (G0110), Address Book Revisions Use Search Type UDC (01/ST) |
The Supplier Master Batch Load automatically loads all JD Edwards EnterpriseOne Suppliers to PeopleSoft Enterprise Vendors. You must manually set up vendor roles in the PeopleSoft Enterprise system only. They are used to set up the vendor's user ID, define the actions that the vendor can complete, and enable the vendor to sign on to the PeopleSoft Enterprise system. |
Loading Master Data for the eProcurement Integration
This section provides overviews of the process of loading JD Edwards EnterpriseOne data into PeopleSoft Enterprise tables and of the incremental synchronization of master data for the eProcurement integration, lists prerequisites, and discusses how to:
Set processing options for Account Master Batch Load (R8909F0901).
Set processing options for Supplier Master Batch Load (R8901F0401).
Set processing options for Item Master Batch Load (R8941F4101).
Set processing options for Item Cost Batch Load (R8941F4105).
Set processing options for Supplier Price Batch Load - F41061 (R8945F4161).
Set processing options for Address Book Master Batch Load (R8901F0101).
Set processing options for Unit of Measure Batch Load (R89F41002).
Run batch integrations in the Integration Server for the eProcurement integration.
Understanding the Process of Loading JD Edwards EnterpriseOne Data into PeopleSoft Enterprise Tables for the eProcurement
Integration
Perform initial loading of this JD Edwards EnterpriseOne data to corresponding PeopleSoft Enterprise tables:
Accounts
Suppliers
Items
Item Cost
Supplier Item Cost
Item Unit of Measure Conversions (optional)
Ship To Locations (facilities)
Users
This table describes the initial data loads that you must perform:
Account Master Batch Load
This initial batch load sends account information from the JD Edwards EnterpriseOne Account Master table (F0901) to the PeopleSoft Enterprise GL_ACCOUNT_TBL table.
The integration server sends the object and subsidiary portions of the JD Edwards EnterpriseOne account number, separated by the account delimiter specified in the integration options, to the PeopleSoft Enterprise system.
Only certain ranges of general ledger account numbers need to be integrated. For example, you might want to load only the expense accounts that support the items or services being placed on the requisitions.
You can limit the general ledger accounts that are integrated for the initial batch load by using the processing options on the Account Master Batch Load program (R8909F0901). Expense accounts tend to fall into certain ranges. For example, if the JD Edwards EnterpriseOne expense accounts are within object account numbers 1000-1499, and 5000-5499, then set up those ranges for the initial batch load and only those object account numbers are integrated with the PeopleSoft Enterprise system.
You can use a realtime event to integrate accounts that are added after the initial batch load. However, the realtime event does not recognize the account range that you defined for the initial batch load and may integrate accounts that are outside of this range. If you prefer not to use a realtime event to integrate account additions, you can run the Account Master Batch Load again, specifying an effective date and the appropriate account range in the processing options of the table conversion program.
The account message is written to a staging table in the PeopleSoft Enterprise system. If the message is validated in the staging table, the process scheduler runs the account loader to update the PeopleSoft Enterprise tables.
SAC_ACCT_LOAD_EIP does not include an action code. Therefore, when you integrate an object account and subsidiary combination that has already been integrated, the system assumes that it is a change to the existing object account and subsidiary combination and overwrites the record in the PeopleSoft Enterprise system.
See Batch Loads.
See Setting Up Integration Options for the eProcurement Integration.
Supplier Master Batch Load
This initial batch load sends suppliers from these JD Edwards EnterpriseOne tables to the PeopleSoft Enterprise VENDOR table:
Supplier Master (F0401)
Address by Date (F0116)
Address Book - Who's Who (F0111)
Address Book - Contact Phone Numbers (F0115)
Electronic Address (F01151)
The supplier-to-vendor flow does not support net change of transactions. To keep vendors synchronized in the JD Edwards EnterpriseOne system and the PeopleSoft Enterprise system, a system administrator must periodically purge the vendors from the PeopleSoft Enterprise system and rerun the supplier initial data load process.
Vendors are automatically assigned the vendor persistence setting Regular in the PeopleSoft Enterprise system.
The alpha name from the f0401batchload.txt file, which comes from the Alpha Name field (ALPH) in the Address Book Master table (F0101), is truncated to 14 characters and is mapped to the VENDOR_NAME_SHORT field in the VENDOR_SYNC EIP. If the combination of the VENDOR_NAME_SHORT and the SETID for a record is not unique, the VENDOR_SYNC cannot process the record and returns an error.
Also, effective-dated supplier records are not supported.
Item Master Batch Load
This initial batch load sends items from the JD Edwards EnterpriseOne Item Master table (F4101) to the PeopleSoft Enterprise Item Master, MASTER_ITEM, INV_ITEM tables.
Note. You must run the Account Master batch load before you run the Item Master batch load so that the items can be attached to valid accounts.
You must run the item master batch integration, including running both the table conversion program and the integration flow, once for each stocking type that you want to integrate. You should not include stocking types that are obsolete.
If you run the item master batch integration a second time for a single stocking type because of a problem with the initial load, you must clear the item cross reference before you rerun the batch integration.
See Setting Up Cross-References for the eProcurement Integration.
The item message is written to a staging table in the PeopleSoft Enterprise system. If the message is validated in the staging table, the process scheduler runs the item loader to update the PeopleSoft Enterprise SRM tables.
The integration does not support configured items (stocking type C). If you load configured items from the JD Edwards EnterpriseOne system to the PeopleSoft Enterprise system, the items are added, but the configuration is not maintained. If you load a parent configured item, the child configurations are not maintained.
Also, effective-dated items are not supported.
If approval processing is not activated in the PeopleSoft Enterprise system, items are automatically set to the Pending Approval (active) status.
Item Cost Batch Load
This initial batch load sends item cost information from the JD Edwards EnterpriseOne Item Cost File table (F4105) to the standard price for an item in the PeopleSoft Enterprise PURCH_ITEM_ATTR table.
Important! You must run the item master initial data load before you run this initial data load.
The process of determining whether to load the cost information for an item depends on the cost level of the item. This table explains the process:
|
Cost Level |
Process |
|
1 |
The table conversion program compares the Purchasing Cost Method (PCSM) to the Cost Method (LEDG) in the Item Cost File table (F4105). If the two cost methods are the same, the record is written to the flat file. |
|
2 |
The table conversion program compares the value in the Branch/Plant processing option on the table conversion program to the Branch Plant (MCU) in the Item Cost File table (F4105). If two branch plants are the same, the table conversion compares the Purchasing Cost Method (PCSM) to the Cost Method (LEDG) in the Item Cost File table (F4105). If the two cost methods are the same, the record is written to the flat file. |
|
3 |
The table conversion program compares the value in the Branch/Plant processing option on the table conversion program the Branch Plant (MCU) in the Item Cost File table (F4105). If the two branch plants are the same, the table conversion compares the primary location (LOCN) from the Item Location File table (F41021) with the primary location (LOCN) from the Item Cost File table (F4105). If the two primary locations are the same, the table conversion compares the Purchasing Cost Method (PCSM) to the Cost Method (LEDG) in the Item Cost File table (F4105). If the two cost methods are the same, the record is written to the flat file. |
Note. If an item cost record fails any test described in the preceding table, that record is not written to the flat file.
The item cost message is written to a staging table in the PeopleSoft Enterprise system. If the message is validated in the staging table, the process scheduler runs the item loader to update the PeopleSoft Enterprise SRM tables.
If you run the item cost batch integration a second time because of a problem with the initial load, you must clear the itemcost key cross reference before you rerun the batch integration.
Supplier Price Batch Load
This initial batch load sends supplier item cost information from the JD Edwards EnterpriseOne Supplier Price/Catalog File table (F41061) to the PeopleSoft Enterprise ITEM_VENDOR_UOM staging tables.
Important! The Supplier Price initial batch load requires that two additional programs are run in the PeopleSoft Enterprise system in order to properly load the tables.
See PeopleSoft Managing Items 8.9 Implementation Guide, “Loading Items.”
The Quantity Break field in JD Edwards EnterpriseOne table F41061 is not sent to the PeopleSoft Enterprise system. If table F41061 contains two records for the same item with the same UOM (unit of measure), one with a Quantity Break and one without, the batch load will fail.
The PeopleSoft Enterprise system assumes that the unit of measure on the first supplier price record is the standard unit of measure. However, the first record sent from the JD Edwards EnterpriseOne system might not reflect the standard unit of measure for the item. After you perform the initial load of supplier prices, you might need to select the Default Unit of Measure option on the Vendor's UOM & Pricing Info page in the PeopleSoft Enterprise system for the correct standard unit of measure for the vendor item price.
See PeopleSoft Enterprise Purchasing 8.9 Implementation Guide, “Setting Up PeopleSoft Purchasing,” Defining Purchasing Item Information, Defining Purchasing Item Attibutes, Defining Purchasing Item Vendor UOM and Pricing Information.
Item Unit of Measure Batch Load
This initial batch load sends unit of measure (UOM) conversion information from the JD Edwards EnterpriseOne Item Units of Measure Conversion Factors to the PeopleSoft Enterprise INV_ITEM_UOM and UOM_TYPE_INV tables.
The Item Unit of Measure Batch Load is optional. If you don’t use PeopleSoft Enterprise eProcurement to procure hard goods, you might not need to use this batch load. If you do procure hard goods, you should either use this batch load or manually set up UOM conversions in PeopleSoft Enterprise that correspond to the UOM conversions you have in JD Edwards EnterpriseOne.
The PeopleSoft Enterprise system supports only unit of measure conversions from or to the primary (lowest) unit of measure. For example, if the primary unit of measure for an item is EA (each), a conversion from BX (boxes) to EA is supported, and a conversion from EA to CA (cases) is supported, but a conversion between BX (boxes) and CA (cases) is not supported.
Also, PeopleSoft Enterprise conversion rates cannot exceed seven integers and eight decimal places. A JD Edwards EnterpriseOne conversion rate with more than seven integers or eight decimals (for example, 12345678.0 or 0.123456789) cannot be integrated with the PeopleSoft Enterprise system.
If the primary unit of measure is equal to the From unit of measure, the integration flow sends the regular conversion factor to PeopleSoft Enterprise. If the primary unit of measure is equal to the To unit of measure, the integration flow sends the inverse conversion factor to PeopleSoft Enterprise.
The item unit of measure message is written to a staging table in the PeopleSoft Enterprise system. If the message is validated in the staging table, the process scheduler runs the item loader to update the PeopleSoft Enterprise SRM tables.
If you run the item unit of measure integration a second time because of a problem with the initial load, you must clear the itemUOM key cross reference before you rerun the batch integration.
Any subsequent additions or changes to item unit of measure conversions that occur in the JD Edwards EnterpriseOne system after the initial batch load is run should be sent to the PeopleSoft Enterprise system by the realtime event. Should you choose to reprocess the initial batch load rather than using the realtime event, additions are processed, but changes produce errors. Deletes are not supported at this time.
Ship To Batch Load
This initial batch load sends address book records for facilities from the JD Edwards EnterpriseOne Address Book Master table (F0101) to the PeopleSoft Enterprise SHIP_TO_TBL table.
You must specify search type F in the processing options of the Address Book Master Batch Load program in order to select only facilities.
The mailing name from the JD Edwards EnterpriseOne system is truncated to 30 characters in the PeopleSoft Enterprise system and the alpha name is truncated to 10 characters in the PeopleSoft Enterprise system.
The E1_Facilities_To_E_SRM_ShipToLocation flow that was used by the initial version of the eProcurement integration has been replaced by the E1_ShipTo_To_E_ShipToLocation flow. Both flows use the R8901F0101 table conversion to extract ship to locations from the JD Edwards EnterpriseOne system. If you are upgrading from the initial version of the eProcurement integration and have already run the E1_Facilities_To_E_SRM_ShipToLocation flow to load ship to locations, you must now run the E1_ShipTo_To_E_ShipToLocation flow using the same ship to records in order to create the shipto key cross reference. In this situation, the E1_ShipTo_To_E_ShipToLocation will not add any records to the PeopleSoft Enterprise system because the records already exist. The sole purpose of running the flow is to create the cross reference. Because the ship to records already exist in the PeopleSoft Enterprise system, the load will error out in the PeopleSoft Enterprise system. You will need to clear out these error logs.
See Setting Up Cross-References for the eProcurement Integration.
If you are using both the Sourcing integration and version two of the eProcurement integration, you must run the batch load for each integration by running the R89F41001 table conversion for the Sourcing integration and the R8901F0101 table conversion for the eProcurement integration. You then run the E1_ShipTo_To_E_ShipToLocation flow twice, specifying the appropriate flat file name in the In File Name - E1 integration option before each time you run the flow.
If you run the ship to batch integration a second time because of a problem with the initial load, you must clear the shipto cross reference before you rerun the batch integration.
User Profile Batch Load
This initial batch load sends user records from the JD Edwards EnterpriseOne Library Lists - User table (F0092) to the PeopleSoft Enterprise REQUESTOR_TBL table.
Understanding the Incremental Synchronization of Master Data for the eProcurement Integration
After you have initially loaded master data from the JD Edwards EnterpriseOne system to the PeopleSoft Enterprise system, you may need to sync up additions or changes to master data that occur in the JD Edwards EnterpriseOne system.
Incremental sync integrations run automatically. When you add, change, or delete an item or item cost record in JD Edwards EnterpriseOne; when you add or change a supplier, ship to location, or unit of measure conversion; or when you add an account in JD Edwards EnterpriseOne.
Note. Some changes to JD Edwards EnterpriseOne companies, business units, and accounts may be to fields that are not integrated with the PeopleSoft Enterprise system. As a result, some incremental sync messages processed by the PeopleSoft Enterprise system might contain no changes to integrated data.
This table describes the incremental syncs provided in this integration:
|
Published Interface Document |
Integration |
EIP |
|
notifySupplierEventPublishDocument |
||
|
notifyGLAccountEventPublishDocument |
||
|
notifyAddressBookPublishDocument |
||
|
notifyShipToEventPublishDocument |
||
|
notifyItemMasterEventPublishDocument |
||
|
notifyItemCostEventPublishDocument |
ITEM_SYNC |
Suppliers
Effective dating of suppliers is not supported; the JD Edwards EnterpriseOne system sends an effective date of January 01, 1900 to the PeopleSoft Enterprise system for all suppliers. Therefore, the supplier incremental sync supports only the effective address, not future addresses.
Also, the supplier incremental sync supports only one address, one contact, and one email address for each supplier.
Accounts
If you use data selection or integration options to include a range of accounts for the initial load, you must use the data selection or integration options for the incremental sync.
The JD Edwards EnterpriseOne system invokes the realtime event for accounts when accounts are added, but not when accounts are changed or deleted. If you delete an account in the JD Edwards EnterpriseOne system, you must also manually delete that account in the PeopleSoft Enterprise system.
Ship To Locations
When you change a ship to location in the JD Edwards EnterpriseOne system, the RTABOUT realtime event is picked up by the E1_AddressBookRTE_To_E_ShipToLocation flow, which sends the data to the LOCATION_SYNC EIP and the SHIPTO_LOCATION EIP.
When you change an address book record for a ship to location in the JD Edwards EnterpriseOne system, you see two instances of the SHIPTO_LOCATION EIP in the PeopleSoft Enterprise Integration Broker Message Monitor, one for inbound and one for outbound. This integration uses only the inbound EIP.
You must enter a value of 2 (Populate Both Contact Information Fields and Array) in the Configure Contact Information processing option 1 to 2 on the Address Book Master Real Time Event Wrapper Application (P010085). If you do not set this processing option, the XML message that is sent to the PeopleSoft Enterprise system does not contain the correct information.
The incremental sync of ship to locations does not support deletions. If you delete a ship to location in the JD Edwards EnterpriseOne system, you must manually inactivate the corresponding ship to location in the PeopleSoft Enterprise system.
Effective dating of ship to locations is not supported.
Items
When you delete an item in the JD Edwards EnterpriseOne system, the item is marked as inactive in the PeopleSoft Enterprise system.
Unit of Measure - Weight and Unit of Measure - Volumes are not supported on the item realtime event. However, these fields are included on the initial load.
Prerequisites
Before you load the master data described in this section:
Set up UTF-8 encoding in the JD Edwards EnterpriseOne system so that the flat files that are created by the table conversion problems will be encoded correctly.
Set up the export folder where the JD Edwards EnterpriseOne table conversions will create the flat files.
Activate realtime events in the JD Edwards EnterpriseOne system.
Setting Processing Options for Account Master Batch Load (R8909F0901)
Processing options enable you to specify the default processing for programs and reports.
Default
|
Date - From |
Specify the beginning date of a valid range of dates that the table conversion uses to select records from the Account Master table (F0901). If you leave this processing option blank, the table conversion selects all records in table F0901. For the initial load of accounts, leave this processing option blank to select all business units. |
|
Time - From |
Specify the beginning time of a valid time range. This processing option works with the Date - From processing option to build the data selection that the table conversion uses to select records from table F0901. For the initial load of accounts, leave this processing option blank to select all business units. |
|
Business Unit - From |
Specify the first business unit in a range of business units. The table conversion selects accounts within the business unit range that you specify. If you leave this processing option blank and complete the Business Unit - To processing option, the system selects accounts with business units up to and including the business unit specified in the Business Unit - To processing option. If you leave both this processing option and the Business Unit - To processing option blank, all business units are valid for selection. |
|
Business Unit - To |
Specify the last business unit in a range of business units. The table conversion selects accounts within the business unit range that you specify. If you leave this processing option blank and complete the Business Unit - From processing option, the system selects accounts with business units from and including the business unit specified in the Business Unit - From processing option. If you leave both this processing option and the Business Unit - From processing option blank, all business units are valid for selection. |
|
Object Account - From |
Specify the first object account in a range of object accounts. The table conversion selects accounts within the object account range that you specify. If you leave this processing option blank and complete the Object Account - To processing option, the system selects accounts with object accounts up to and including the object specified in the Object Account - To processing option. If you leave both this processing option and the Object Account - To processing option blank, all object accounts are valid for selection. |
|
Object Account - To |
Specify the last object account in a range of object accounts. The table conversion selects accounts within the object account range that you specify. If you leave this processing option blank and complete the Object Account - From processing option, the system selects accounts with object accounts from and including the object specified in the Object Account - From processing option. If you leave both this processing option and the Object Account - From processing option blank, all object accounts are valid for selection. |
|
Subsidiary |
Specify the subsidiary that the table conversion uses to select accounts. If you leave this processing option blank, all subsidiaries are valid for selection. |
Setting Processing Options for Supplier Master Batch Load (R8901F0401)
Processing options enable you to specify the default processing for programs and reports.
Default
|
1. Date - From |
Specify the beginning date of a valid range of dates that the table conversion uses to select records from the Supplier Master table (F0401). If you leave this processing option blank, the table conversion selects all records in the F0401 table. For the initial load of suppliers, leave this processing option blank to select all business units. |
|
2. Time - From |
Specify the beginning time of a valid time range. This processing option works with the Date - From processing option to build the data selection that the table conversion uses to select records from the F0401 table. For the initial load of suppliers, leave this processing option blank to select all business units. |
Setting Processing Options for Item Master Batch Load (R8941F4101)
Processing options enable you to specify the default processing for programs and reports.
Default
|
Date - From |
Specify the beginning date of a valid range of dates that the table conversion uses to select records from the Item Master table (F4101). If you leave this processing option blank, the table conversion selects all records in the F4101 table. For the initial load of items, leave this processing option blank to select all business units. |
|
Time - From |
Specify the beginning time of a valid time range. This processing option works with the Date - From processing option to build the data selection that the table conversion uses to select records from the F4101 table. For the initial load of items, leave this processing option blank to select all business units. |
|
Stocking Type |
Specify the stocking type for nonstock transactions. The default value is N. Note. This integration supports only nonstock transactions. |
Setting Processing Options for Item Cost Batch Load (R8941F4105)
Processing options enable you to specify the default processing for programs and reports.
Default
|
Default Business Unit |
Specify the default branch plant to be used when creating the flat file for items at cost level 2 or 3. If the branch plant you enter does not match the branch plant of the selected record, the record is not written to the flat file. If you leave this processing option blank, the item cost flat file is generated for all branch plants. |
|
Default Location |
Specify the default location for items at cost level 3. Enter 1 to select item cost records based on their primary location as defined in the Item Location File table (F41021). Leave this processing option blank to create the item cost flat file for all locations. |
|
Stocking Type |
Specify the stocking type for nonstock transactions. The default value is N. |
Setting Processing Options for Supplier Price Batch Load - F41061 (R8945F4161)
Processing options enable you to specify the default processing for programs and reports.
Default
|
Date - From |
Specify the beginning date of a valid range of dates that the table conversion uses to select records from the Supplier Price/Catalog File table (F41061). If you leave this processing option blank, the table conversion selects all records in the F41061 table. For the initial load of supplier price, leave this processing option blank to select all business units. |
|
Time - From |
Specify the beginning time of a valid time range. This processing option works with the Date - From processing option to build the data selection that the table conversion uses to select records from the F41061 table. For the initial load of supplier price, leave this processing option blank to select all business units. |
Setting Processing Options for Address Book Master Batch Load (R8901F0101)
Processing options enable you to specify the default processing for programs and reports.
Default
|
1. Date - From |
Specify the beginning date of a valid range of dates that the table conversion uses to select records from the Address Book Master table (F0101). If you leave this processing option blank, the table conversion selects all records in the F0101 table. For the initial load of facilities, leave this processing option blank to select all business units. |
|
2. Time - From |
Specify the beginning time of a valid time range. This processing option works with the Date - From processing option to build the data selection that the table conversion uses to select records from the F0101 table. For the initial load of facilities, leave this processing option blank to select all business units. |
|
3. Search Type |
Specify the search type that the table conversion uses to select records from the F0101 table. For the PeopleSoft Enterprise eProcurement to JD Edwards EnterpriseOne Procurement integration, specify the search type for Facilities. |
Setting Processing Options for Unit of Measure Batch Load (R89F41002)
Processing options enable you to specify the default processing for programs and reports.
Default
|
Business Unit |
Specify the branch/plant that the table conversion uses to select records from the Item Units of Measure Conversion Factors table (F41002). If you leave this processing option blank, the table conversion selects all records in the F41002 table. For the initial load of unit of measure conversions, leave this processing option blank to select all branch/plants. |
Running Batch Integrations in the Integration Server for the eProcurement Integration
Use JD Edwards EnterpriseOne WSG Integration Server or WSG Developer to invoke the batch integrations. The batch integration contains an integration service, which performs the necessary data transformations and exports an XML file that the PeopleSoft Enterprise system can receive.
To run the batch integrations manually, invoke these services:
|
Integration Service |
Navigation |
|
PSFT_JD Edwards EnterpriseOne_SRM.InitialBatchLoads.E1_ItemMaster_To_E_Item:convert_E1_ItemMaster_To_E_Item |
|
|
PSFT_JD Edwards EnterpriseOne_SRM.InitialBatchLoads.E1_ItemCost_To_E_Item:convert_E1_ItemCost_To_E_Item |
|
|
PSFT_JD Edwards EnterpriseOne_SRM.InitialBatchLoads.E1_Supplier_To_E_Vendor:convert_E1_Supplier_To_E_Vendor_And_Dispatch |
|
|
PSFT_JD Edwards EnterpriseOne_SRM.InitialBatchLoads.E1_SupplierItemCost_To_E_SRM_ItemPriceList:convertSupplierItemCostToItemPriceList |
|
|
PSFT_JD Edwards EnterpriseOne_SRM.InitialBatchLoads.E1_Account_To_E_SRM_Account:convertAccountToAccountLoad |
|
|
PSFT_JD Edwards EnterpriseOne_SRM, InitialBatchLoads, E1_ShipTo_To_E_ShipToLocation, convert_ShipTo_To_ShipToLocation |
|
|
PSFT_JD Edwards EnterpriseOne_SRM, InitialBatchLoads, E1_ItemUOM_To_E_ItemUOM, convert_E1_ItemUOM_To_E_ItemUOM |
|
|
PSFT_JD Edwards EnterpriseOne_SRM.InitialBatchLoads.E1_UserProfile_To_E_SRM_Requester:convertUserProfileToRequester |
Note. Some firewalls and network settings can interfere with the retrieval of the text files from the designated network folder if on a different domain. If this problem occurs, copy the text files to a share drive on the same network domain as the WSG Integration Server.
See Also
webMethods Integration Server Administrator's Guide 6.1, "Managing Services,” Working with Services, Testing Services
Setting Up Cross-References for the eProcurement Integration
This section discusses how to:
Set up key cross-references for the eProcurement integration.
Set up code cross-references for the eProcurement integration.
Setting Up Key Cross-References for the eProcurement Integration
The integration requires that key cross-references be set up in the JD Edwards EnterpriseOne WSG Cross-Reference database. The system creates all of these key cross-references except for the businessunit cross-reference, which you must create manually.
Some of the key cross references are used to determine whether a record that is being sent from the JD Edwards EnterpriseOne system is being added or changed. If the record has a the key that is already listed in the cross-reference, the record is considered to be a change. If the record's key is not already listed in the cross-reference, the record is considered to be an add.
|
Application ID |
Object ID |
Comments |
|
E-SRM |
businessunit |
You must manually set up this key cross-reference between JD Edwards EnterpriseOne business units and PeopleSoft Enterprise business units. In the Native Key field, specify business units from the BUSINESS_UNIT field in the PeopleSoft Enterprise system. In the Canonical Key field, specify business units from the Business Unit field (MCU) of the Business Unit Master table (F0006) in the JD Edwards EnterpriseOne system. |
|
E-SRM |
department |
You must manually set up this key cross-reference between the JD Edwards EnterpriseOne business units that the employee expenses will be charged to, branch/plants, or both and PeopleSoft Enterprise departments. In the Native Key field, specify departments from the DEPT_ID field in the PeopleSoft Enterprise system. In the Canonical Key field, specify business units from the Business Unit field (MCU) in the Business Unit Master table (F0006) or in the Item Branch File table (F4102) in the JD Edwards EnterpriseOne system. |
|
E-SRM |
electronicaddresslinenumber |
The system creates this key cross-reference during the initial load of suppliers. This cross-reference is used by the incremental sync of suppliers to determine whether the email address that is being sent from the JD Edwards EnterpriseOne system to the PeopleSoft Enterprise system is being added or changed. The key is formatted as follows: vendorID|who's who line number|email line number Note. The who's who line number is always 1. |
|
E-SRM |
item |
The system creates this key cross-reference during the initial load of items. This cross-reference is used by the incremental sync of suppliers to determine whether the item record that is being sent from the JD Edwards EnterpriseOne system to the PeopleSoft Enterprise system is being added or changed. The key is formatted as follows: item number |
|
E-SRM |
itemcost |
The system creates this key cross-reference during the initial load of item cost information. This cross-reference is used by the incremental sync of item cost information to determine whether the item cost information that is being sent from the JD Edwards EnterpriseOne system to the PeopleSoft Enterprise system is being added or changed. The key is formatted as follows: item number |
|
E-SRM |
itemUOM |
The system creates this key cross-reference during the initial load of item unit of measure conversions. This cross-reference is used by the incremental sync of item unit of measure conversions to determine whether the item unit of measure conversion that is being sent form the JD Edwards EnterpriseOne system to the PeopleSoft Enterprise system is being added or changed. The key is formatted as follows: Item number|from unit of measure|to unit of measure|primary unit of measure |
|
E-SRM |
phonelinenumber |
The system creates this key cross-reference during the initial load of suppliers. This cross-reference is used by the incremental sync of suppliers to determine whether the phone number that is being sent from the JD Edwards EnterpriseOne system to the PeopleSoft Enterprise system is being added or changed. The key is formatted as follows: vendorID|who's who line number|phone line number Note. The who's who line number is always 1. |
|
E-SRM |
shipto |
The system creates this key cross-reference during the initial load of ship to locations. Because ship to information can be loaded from different sources for the PeopleSoft Enterprise eProcurement to JD Edwards EnterpriseOne Procurement integration and the PeopleSoft Enterprise Strategic Sourcing to JD Edwards EnterpriseOne Procurement integration, this cross-reference is used by both the initial load and incremental sync of ship to locations to determine whether the phone number that is being sent from the JD Edwards EnterpriseOne system to the PeopleSoft Enterprise system is being added or changed. The key is formatted as follows: address book number |
For example, you might have business units 30 and M30 set up in the JD Edwards EnterpriseOne system. Business unit M30 is set up as a branch/plant and maps to business unit US001 in the PeopleSoft Enterprise system. Cost center 30 in the JD Edwards EnterpriseOne system maps to department 5000 in the PeopleSoft Enterprise system. In this situation, you would set up key cross-references in this way:
|
Object ID |
Native Code |
Canonical Code |
|
businessunit |
US001 |
M30 |
|
department |
5000 |
30 |
Setting Up Code Cross-References for the eProcurement Integration
You set up code cross-references in the JD Edwards EnterpriseOne WSG Cross-Reference database. To cross reference phone types, use Application ID E-SRM and the Object ID phonetype. Specify the PeopleSoft Enterprise value as the Native Code and the JD Edwards EnterpriseOne value as the Canonical Code, for example:
|
Application ID |
Object ID |
Native Code |
Canonical Code |
|
E-SRM |
phonetype |
|
Specify codes from UDC 01/PH in the JD Edwards EnterpriseOne system. |
Note. A blank phone type in the JD Edwards EnterpriseOne system is invalid when running this integration. JD Edwards EnterpriseOne phone types are listed in UDC 01/PH.