Prerequisites for Performing EDI TS130 Transcript Transactions

The EDI Manager provides the tools you need to manage electronic commerce transactions with your trading partners. To assist you in setting up the EDI Manager for recruiting and admissions application and transcript transactions, we have created some sample definitions in the EDI Manager. However, before processing EDI transactions, you might need to modify the setup to fit your particular needs. Therefore, it is important that you become familiar with PeopleSoft EDI architecture and recruiting and admissions processes to understand the implications of your EDI implementation decisions. The following paragraphs explain how this information can be set up.

When a trading partner submits an EDI transaction, it needs to address it to a specific business unit. In other words, the EDI agent needs to know in some way to which business unit to forward the transaction. Therefore, you must define entity codes that tell the EDI Manager where to forward the transaction. This PeopleSoft system includes sample entity codes for admissions transcript and application transactions, as well as sample internal and external partner definitions.

• The sample entity code provided for the Admissions Transcript Transaction (TS130) is ADTR - Admission Transcript Process.

• Two sample entity codes are provided for the Application for Admissions Transaction (TS189): ADAP - Admissions Applicant Processing and ADST - Admissions Applicant Student.

• The sample internal partner definition provided (for both the EDI TS130 and TS189 transactions) is Admissions - Admissions Office.

• The sample external partner definition provided (for both the EDI TS130 and TS189 transactions) is ADM_EDI_STX - Admissions EDI Supply Tech. As mentioned earlier, you might use another external partner as your EDI translator.

When you receive an EDI transaction from a trading partner, the first record of the transaction includes a Transaction ID that identifies the transaction type. The EDI agent uses the transaction ID, in conjunction with the trading partner ID, to determine which inbound map to use to process the transaction data. Similarly, when you initiate an outbound transaction, the EDI agent puts the appropriate transaction ID in the first transaction record so that the recipient knows what kind of transaction you have sent. The PeopleSoft system includes sample transaction definitions, partner profile definitions and conversion data profiles.

• The sample transaction definition provided for your ADM_TRNS_130 Admissions Transcript Transaction is ADM_TRNS_TS130 Inbound - Admissions Transcript Transaction.

• The sample transaction definition provided for your ADM_TRNS_189 Admissions Applicant Transaction is ADM_TRNS_TS189 Inbound - Admissions Applicant Transaction.

• The sample partner profile definition provided (for both the EDI TS130 and TS189 transactions) is ADM_EDI_P - Admissions EDI Transaction Profile.

• The sample conversion data profile provided is EDI_CONV - EDI TS130/TS189. Conversion Profile lists the conversion values used in your EDI load processing (for both the EDI TS130 and TS189 transactions).

Electronic commerce maps specify how the EDI Agent transfers data between PeopleSoft business documents and the staging tables in the PeopleSoft database. The EDI agent uses inbound maps to transfer data from PeopleSoft business documents to the staging tables, in preparation for processing by your Recruiting and Admissions application. PeopleSoft has created sample inbound map definitions.

• The sample inbound map definition provided for the Admissions Transcript Transaction (ADM_TRNS_TS13O) is EC Map ID TS130_MAP.

• The sample inbound map definition provided for the Admissions Applicant Transaction (ADM_TRNS_TS189) is EC Map ID TS189_MAP.

When you add a trading partner, you assign to it a map profile, which lists the electronic commerce maps that the EDI agent can use to process transactions from the partner. The PeopleSoft system includes sample data mapping profile definitions.

The example data mapping profile definition provided is ADM_EDIMP - Admissions EDI Map Profiles. This definition lists the map assignments for the Admissions Transcript Transaction (ADM_TRNS_TS13O) and the Admissions Applicant Transaction (ADM_TRANS_TS189).