This chapter includes these topics:
Section 35.2, "Address Book Business Services - AddressBookManager"
Section 35.3, "(Release 9.1 Update) Address Book Business Services - LatLongProcessor"
Section 35.6, "Address Book Batch Export Programs (Release 9.1 Update)"
This chapter provides detailed information about the business interfaces that are available for the Address Book business object.
This table lists all of the available interface components:
| Interface Type | Available Interfaces |
|---|---|
| Business Services | The AddressBookManager web service (JP010000) manages the processing of these address book-related web service operations:
(Release 9.1 Update) The LatLongProcessor web service (JC011500) uses the Oracle Location Service to retrieve and store the latitude and longitude of the current mailing address for selected address book records.The following business service is available for the Address Book business service:
|
| Real-Time Events | This list includes the real-time events for the Address Book business object:
|
| Batch Import Programs | This list includes the batch import programs for the Address Book business object: |
| Additional Interfaces | The Address Book business object also uses the following business interfaces:
See Setting Processing Options for Address Book MBF (P0100041). |
|
Note: You can find additional technical information about each type of business interface component. For additional descriptions of the information available, and instructions for finding this information, see Chapter 5, "Accessing Additional Information for Business Interface Components." |
The AddressBookManager web service (JP010000) manages the processing of the address book-related web service operations. This table includes a description of the address book web service operations:
To access Javadoc for the Address Book Manager web service and its related operations, review these Javadoc packages:
JP010000 (AddressBookManager)
J0100001 (processAddressBook)
J010001 (processAddressBookV2)
J0100002 (getAddressBook)
J0100002 (getAddressBookV2
J0100003 (processContact)
J0100004 (getContact)
Before you can use the Address Book Manager web service, or any of the related web service operations, you must first install and configure the JD Edwards EnterpriseOne Address Book system.
Additionally, you must set up business service properties that are used by all Address Book web service operations that process phone and electronic mail address information. This table lists the business service properties that must be set up:
| Group | Key | Description | Default Value |
|---|---|---|---|
| J0100005 | J0100005_PHONE_ERROR_PREFIX | Use this business service property to specify the prefix that the system uses for phone error messages. | Phone Record Sent |
| J0100006 | J0100006_ELECADDR_ERROR_PREFIX | Use this business service property to specify the prefix that the system uses for electronic address error messages. | Electronic Address Record Sent |
The getAddressBook web service operation is a database query operation that enables consumers to retrieve and review address, phone, and electronic mail information for specified entities from the JD Edwards EnterpriseOne Address Book system.
The operation returns zero to many records if it completes successfully. If the operation encounters errors while processing address information, processing stops and those errors and warnings are returned to the consumer. If the operation encounters errors while processing phone or electronic mail information, the errors are converted to warnings, processing continues, and the warnings are returned to the consumer.
Before you use this operation, you can set business service properties to specify how the system retrieves data from the JD Edwards EnterpriseOne database. This table includes information about the business service properties that the getAddressBook operation uses:
| Group | Key | Description | Default Value |
|---|---|---|---|
| J0100002 | J0100002_MAX_ROWS | Use this operation to specify the maximum number of records that the operation returns. | 100 |
|
Note: It is recommended that users configure this business service property, and use a value other than 0 (zero). Setting this property to 0 enables the operation to return all matching records. Additionally, it is recommended that you pass in selection criteria when processing this operation. If you do not pass in selection criteria, and you set this business property to 0, you might encounter significant performance issues.Additionally, this operation uses a joined view of the F0101, F0116, and F0150 tables when retrieving data. The system enforces a one-to-one relationship between records from the F0101 and F0116, and a one-to-many relationship between the F0101 and the F0150 during initial record retrieval. After all records have been retrieved, the operation deletes records with duplicate address book numbers (AN8). This business service property is enforced during the initial record retrieval, before duplicate records are deleted. Therefore, the actual number of records that the operation returns might be less than the maximum number of rows specified. |
See JD Edwards EnterpriseOne Tools Business Services Development Methodology Guide.
This table includes information that can help determine whether the getAddressBook operation is functioning correctly:
| Question | Answer |
|---|---|
| How can I tell if the operation completes successfully? | If the operation completes successfully, the system displays zero to many records, based on the selection criteria that the consumer passes in. If the operation fails, an error is returned to the consumer.
The records that are returned to the consumer include all of the fields that are listed in the response interface for this operation. However, some of those fields can contain blank or zero values, depending on the data that exists in the JD Edwards EnterpriseOne system. At a minimum, the system returns non-zero values for these fields:
|
| If I encounter errors while processing a transaction, do I need to reverse the transaction? | This is a database query operation that does not perform transactions. If you encounter errors during processing, review your search criteria and business service property settings and try your query again. If the operation does not return any records, verify that records matching your query exist in the JD Edwards EnterpriseOne database. |
| Does this operation use record reservation? | No. The operation does not reserve records within the JD Edwards EnterpriseOne system during processing. |
Review the information in the getAddressBook section of this chapter before using the getAddressBookV2 web service operation. All of the information in the getAddressBook section also applies to the getAddressBookV2 operation.
The getAddressBookV2 operation is a version of the getAddressBook web service operation. This web service operation is used to retrieve address book records with associated GLNs. This version executes the getAddressBook (J010002) web service operation.
The processAddressBook web service operation is an inbound transaction operation that enables consumers to:
Add records to the JD Edwards EnterpriseOne Address Book system.
Delete records from the JD Edwards EnterpriseOne Address Book system.
Change records in the JD Edwards EnterpriseOne Address Book system.
The operation uses the AddressBookMasterMBF business function (N0100041) to process information. If the operation encounters errors while processing address book information, processing stops and all errors and warnings are returned to the consumer. If the operation encounters errors while processing phone or electronic mail information, the errors are converted into warnings, processing continues, and the warnings are returned to the consumer.
This section discusses the functionality that the processAddressBook operation supports.
|
Note: If functionality is not explicitly documented as supported functionality, it is to be understood that the functionality is not supported by the integration solution. |
This operation enables consumers to add, change, or delete address book records. The operation also enables users to add, change, or delete the Who's Who records in the Address Book. These records contain a value of 0 (zero) in the Who's Who Line Number field. The operation also processes phone and electronic mail information for the Who's Who record with line number zero.
This operation does not support related person or alternate address processing for an address book record.
Before you use this operation, you can set business service properties to specify how the system processes address book information. This table includes information about the business service properties that the processAddressBook operation uses:
| Group | Key | Description | Default Value |
|---|---|---|---|
| J0100001 | J0100001_AB_MBF_VERSION | Use this business service property to specify the version of the AddressBookMasterMBF (N0100041) the operation uses to process address book information. | ZJDE0001 |
See JD Edwards EnterpriseOne Tools Business Services Development Methodology Guide.
This table includes information that can help determine whether the processAddressBook operation is functioning correctly:
| Question | Answer |
|---|---|
| How can I tell if the operation completes successfully? | If the operation completes successfully, the user receives a return message that includes the records that were added, changed or updated. The records that are returned to the consumer include all of the fields that are listed in the response interface for this operation. However, some of those fields can contain blank or zero values, depending on the data that exists in the JD Edwards EnterpriseOne system.
At a minimum, the system returns non-zero values for these fields:
|
| If I encounter errors while processing a transaction, do I need to reverse the transaction? | This operation uses standard transaction processing. If the system encounters errors while processing address book information, no data in the JD Edwards EnterpriseOne system is updated. No manual updates are required.
If the operation encounters errors while processing phone or electronic mail information, those errors are converted to warnings and the warnings are returned to the consumer. These warnings do not stop the processAddressBook operation from processing, but the phone or electronic address that causes the error is not processed. |
| Does this operation use record reservation? | No. The operation does not reserve records within the JD Edwards EnterpriseOne system during processing. |
Review the information in the processAddressBook section of this chapter before using the processAddressBookV2 web service operation. All of the information in the processAddressBook section also applies to the processAddressBookV2 operation.
The processAddressBookV2 operation is a version of the processAddressBook web service operation. This web service operation is used to add, update, or delete address book records with associated GLNs. This version executes the processAddressBook (J010001) web service operation.
The getContact web service operation is a database query operation that enables consumers to retrieve and review contact, alternate address, phone, and electronic mail information for specified contacts from the JD Edwards EnterpriseOne Address Book system.
The operation returns zero to many records if it completes successfully. If the operation encounters errors while processing contact information, processing stops and those errors and warnings are returned to the consumer. If the operation encounters errors while processing phone or electronic mail information, the errors are converted to warnings, processing continues, and the warnings are returned to the consumer.
Before you use this operation, you can set business service properties to specify how the system retrieves data from the JD Edwards EnterpriseOne database. This table includes information about the business service properties that the getContact operation uses:
| Group | Key | Description | Default Value |
|---|---|---|---|
| J0100004 | J0100004_MAX_ROWS | Use this operation to specify the maximum number of records that the operation returns. | 100 |
|
Note: It is recommended that users configure this business service property, and use a value other than 0 (zero). Setting this constant to 0 enables the operation to return all matching records. Additionally, it is recommended that you pass in selection criteria when processing this operation. If you do not pass in selection criteria, and you set this business property to 0, you might encounter significant performance issues. |
See JD Edwards EnterpriseOne Tools Business Services Development Methodology Guide.
This table includes information that can help determine whether the getAddressBook operation is functioning correctly:
| Question | Answer |
|---|---|
| How can I tell if the operation completes successfully? | If the operation completes successfully, the system displays zero to many records, based on the selection criteria that the consumer passes in. If the operation fails, an error is returned to the consumer.
The records that are returned to the consumer include all of the fields that are listed in the response interface for this operation. However, some of those fields can contain blank or zero values, depending on the data that exists in the JD Edwards EnterpriseOne system. At a minimum, the system returns non-zero values for these fields:
|
| If I encounter errors while processing a transaction, do I need to reverse the transaction? | This is a database query operation that does not perform transactions. If you encounter errors during processing, review your search criteria and business service property settings and try your query again. If the operation does not return any records, verify that records matching your query exist in the JD Edwards EnterpriseOne database. |
| Does this operation use record reservation? | No. The operation does not reserve records within the JD Edwards EnterpriseOne system during processing. |
The processContact web service operation is an inbound transaction operation that enables consumers to add, change, or delete records to and from these JD Edwards EnterpriseOne tables:
Who's Who table (F0111)
Phones table (F0115)
Electronic Addresses table (F01151)
Alternate Addresses table (F01161)
The operation uses the WhosWhoMBF (N0100087) to process contact information. If the operation encounters errors while processing contact information, processing stops and the errors are returned to the consumer. If the operation encounters errors while processing phone or electronic mail information, the errors are converted to warnings, processing continues, and the warnings are returned to the consumer.
This section discusses the functionality that the processContact operation supports.
|
Note: If functionality is not explicitly documented as supported functionality, it is to be understood that the functionality is not supported by the integration solution. |
The operation does not support any country-specific localization functionality. Additionally, the operation does not enable users to add, change or delete a contact's related person information.
Before you use this operation, you can set business service properties to specify how the system processes contact data. This table includes information about the business service properties that the processContact operation uses:
| Group | Key | Description | Default Value |
|---|---|---|---|
| J0100003 | J0100003_WHOSWHO_MBF_VERSION | Use this business service property to specify the version of the Who'sWhoMBF (N0100087) that the operation uses to process contact information. | ZJDE0001 |
See JD Edwards EnterpriseOne Tools Business Services Development Methodology Guide.
This table includes information that can help determine whether the processContact operation is functioning correctly:
| Question | Answer |
|---|---|
| How can I tell if the operation completes successfully? | If the operation completes successfully, the user receives a return message that includes the records that were changed or updated.
The records that are returned to the consumer include all of the fields that are listed in the response interface for this operation. However, some of those fields can contain blank or zero values, depending on the data that exists in the JD Edwards EnterpriseOne system. At a minimum, the system returns non-zero values for these fields:
|
| If I encounter errors while processing a transaction, do I need to reverse the transaction? | This operation uses standard transaction processing. If the system encounters errors while processing contact information, no data in the JD Edwards EnterpriseOne system is updated. No manual updates are required.
If the operation encounters errors while processing phone or electronic mail information, those errors are converted to warnings and the warnings are returned to the consumer. These warnings do not stop the processContact operation from processing, but the phone or electronic address that causes the error is not processed. |
| Does this operation use record reservation? | No. The operation does not reserve records within the JD Edwards EnterpriseOne system during processing. |
The lookupAddressBook web service operation is an database query operation that enables consumers to retrieve and review address book information from the JD Edwards EnterpriseOne database. This operation retrieves these items for each business unit, if the data exists in the database:
EntityTypeCode
EntityName
Entity, which includes:
EntityId
LongId
EntityTaxId
CategoryCodesAddressBook, which includes CategoryCode001 through CategoryCode030.
Before you use this operation, you can set business service properties to specify how the system processes contact data. This table includes information about the business service properties that the lookupAddressBook operation uses:
| Group | Key | Description | Default Value |
|---|---|---|---|
| J0100009 | J0100009_MAX_ROWS | Use this business service property to specify the maximum number of F0101 records the operation can return for a query. | 100 |
See JD Edwards EnterpriseOne Tools Business Services Development Methodology Guide.
This table includes information that can help determine whether the lookupAddressBook operation is functioning correctly:
| Question | Answer |
|---|---|
| How can I tell if the operation completes successfully? | If the operation completes successfully, zero or more records are returned, based on the selection criteria.
The records that are returned to the consumer include all of the fields that are listed in the response interface for this operation. However, some of those fields can contain blank or zero values, depending on the data that exists in the JD Edwards EnterpriseOne system. At a minimum, the system returns non-zero values for these fields:
|
| If I encounter errors while processing a transaction, do I need to reverse the transaction? | This is a database query operation that does not perform transactions. If you encounter errors during processing, review your search criteria and business service property settings and try your query again. If the operation does not return any records, verify that records matching your query exist in the JD Edwards EnterpriseOne database. |
| Does this operation use record reservation? | No. The operation does not reserve records within the JD Edwards EnterpriseOne system during processing. |
The LatLongProcessor web service (JC011500) processes the latitude and longitude of the current mailing address for selected address book records. This table includes a description of the address book business service.
| Operation | Description |
|---|---|
| getProcessLatLong | Use this business service to retrieve and update latitude and longitude information from the JD Edwards EnterpriseOne Address Book system. |
Before using the Address Book web service, or any of the related web service operations, you must first install and configure the JD Edwards EnterpriseOne Address Book system.
You must also set the value of Enable Location Services to Yes in the Work with EnterpriseOne System Control (P99410) program.
The getProcessLatLong business service runs on the Oracle WebLogic Server (WLS) or the Web Application Server (WAS) platform and reads the data stored in the Address Book Geo Code (F0116) table. The EnterpriseOne Enterprise Server collects the data required from the JD Edwards EnterpriseOne Address Book Geo Code (F0116) table and then calls the getProcessLatLong business service that communicates with Oracle Location Services to convert the address book record's address to a latitude and longitude. The getProcessLatLong business service operation enables users to retrieve address book geocodes for specified entities from the JD Edwards EnterpriseOne Address Book system.
For each record in the F0116 table, when a record is in error, EV01 is set to 1. Otherwise, when a record is successfully processed, EV01 is set to 0 and written to the F0119 table.
This section describes the available real-time events associated with the Address Book business object, which include:
RTABOUT is a container event that includes these single events:
RTABOUT2 is a container event that includes these single events:
RTPCOUT is a container event that includes these single events:
RTPCOUT2 is a container event that includes these single events:
RTSHPOUT is a container event that includes these single events:
RTABOUT is a container event generated by the JD Edwards EnterpriseOne system to notify third-party systems about changes to the address book record. RTABOUT is a container event for RTABHDR, RTABPHOUT, and RTABEAOUT.
| Event Type | Event Description | Event Category | Event Aggregate | Product Code |
|---|---|---|---|---|
| RTABOUT | Address Book Master | RTE | Container
Container event for:
|
01 |
Please see the appropriate real-time events that are contained by this event for information about the event fields and conceptual approach.
These are the objects that can initiate the event, and any single event contained by this event:
B0100087 - Who's Who MBF
B0100089 - Electronic Address
B0100090 - Phones
N0100041 - Address book MBF
P01111 – Contact Information
SPECIAL SETUP
RTABOUT has some additional special setup requirements due to the logic in the real-time wrapper.
The processing options for version ZJDE0001 of the Address Book Master Real Time Event Wrapper Application program (P0100085) determine which phone and email records are sent. The purpose of these processing options is to enable filtering of the outbound event, RTABOUT.
This table explains the processing options:
Enter a code to specify how you want to send contact information. Values are:
0, blank, or null: The system sends only primary contact information for an address book record as single fields. It sends the first telephone number, fax number, and email address of an address book record that matches the type specified in the other processing options.
1: Regardless of the types specified in the other processing options, the system sends the complete collection of contact information, including primary contact information, for an address book record in one group.
2: The system sends primary contact information in single fields, and the complete collection of contact information in a group. This value is a combination of values 0 and 1.
Indicate either the location or use of a telephone number. Values are defined in user-defined code (UDC) table 01/PH (Phone Type).
Specify the phone type for the telephone number to use for faxes. Values are defined in UDC table 01/PH (Phone Type).
Specify the electronic address type that the system uses for an individual or an entity for internet communications. Values are defined in UDC table 01/ET (Electronic Address Type).
RTABHDR is a single event that provides address book header information within the RTABOUT container event. RTABHDR is generated only when RTABOUT is generated.
| Event Name | Event Description | Event Type | Event Category | Product Code | Data Structure | Event Relationship |
|---|---|---|---|---|---|---|
| RTABHDR | AB Header | RTE | Single | 01 | D0100085A: Address Book Master Real Time | Included in container event RTABOUT. |
Conceptual Approach
An address book record added, modified, or deleted in the JD Edwards EnterpriseOne system creates, modifies, or deletes a record in the Address Book tables (Address Book Master, F0101; Address Book - Who's Who, F0111; Contact Information, F01111; Address Book - Contact Phone Numbers F0115; Electronic Address, F01151; Address by Date, F0116).
RTABPHOUT is a single event that provides address book phone information within the RTABOUT container event. RTABPHOUT is generated only when RTABOUT is generated.
| Event Name | Event Description | Event Type | Event Category | Product Code | Data Structure | Event Relationship |
|---|---|---|---|---|---|---|
| RTABPHOUT | AB Phone | RTE | Single | 01 | D0100085B: Address Book Master Phones Wrapper Data Structure | Included in container event RTABOUT. |
Conceptual Approach
An address book phone record added, modified, or deleted in the JD Edwards EnterpriseOne system creates, updates, or deletes a record in the Address Book - Contact Phone Numbers (F0115).
RTABEAOUT is a single event that provides address book email information within the RTABOUT container event. RTABEAOUT is generated only when RTABOUT is generated.
| Event Name | Event Description | Event Type | Event Category | Product Code | Data Structure | Event Relationship |
|---|---|---|---|---|---|---|
| RTABEAOUT | AB Electronic Address | RTE | Single | 01 | D0100085C: Address Book Master Email Wrapper Data Structure | Included in container event RTABOUT. |
Conceptual Approach
An address book email record added, modified, or deleted in the JD Edwards EnterpriseOne system creates a new record in the Electronic Address (F01151) table.
RTABOUT2 is a container event generated by the JD Edwards EnterpriseOne system to notify third-party systems about changes to the address book record. RTABOUT is a container event for RTABHDR2, RTABPHOUT2, and RTABEAOUT2.
| Event Type | Event Description | Event Category | Event Aggregate | Product Code |
|---|---|---|---|---|
| RTABOUT2 | Address Book Master Version 2 | RTE | Container
Container event for:
|
01 |
Please see the appropriate real-time events that are contained by this event for information about the event fields and conceptual approach
These are the processes that can initiate the event, and the single events contained by this event:
B0100087 - Who's Who MBF
B0100089 - Electronic Address
B0100090 - Phones
N0100041 - Address book MBF
P01111 – Contact Information
SPECIAL SETUP
RTABOUT2 has some additional special setup requirements due to the logic in the real-time wrapper.
The processing options for version ZJDE0001 of the Address Book Master Real Time Event Wrapper Application program (P0100100) determine which phone and email records are sent. The purpose of these processing options is to enable filtering of the outbound event, RTABOUT2.
This table explains the processing options:
Enter a code to specify how you want to send contact information. Values are:
0, blank, or null: The system sends only primary contact information for an address book record as single fields. It sends the first telephone number, fax number, and email address of an address book record that matches the type specified in the other processing options.
1: Regardless of the types specified in the other processing options, the system sends the complete collection of contact information, including primary contact information, for an address book record in one group.
2: The system sends primary contact information in single fields, and the complete collection of contact information in a group. This value is a combination of values 0 and 1.
Indicate either the location or use of a telephone number. Values are defined in user-defined code (UDC) table 01/PH (Phone Type).
Specify the phone type for the telephone number to use for faxes. Values are defined in UDC table 01/PH (Phone Type).
Specify the electronic address type that the system uses for an individual or an entity for internet communications. Values are defined in UDC table 01/ET (Electronic Address Type).
RTABHDR2 is a single event that provides address book header information within the RTABOUT2 container event. RTABHDR2 is generated only when RTABOUT2 is generated.
| Event Name | Event Description | Event Type | Event Category | Product Code | Data Structure | Event Relationship |
|---|---|---|---|---|---|---|
| RTABHDR2 | AB Header Version 2 | RTE | Single | 01 | D0100100A: Address Book Master Real Time | Included in container event RTABOUT |
Conceptual Approach
An address book record added, modified, or deleted in the JD Edwards EnterpriseOne system creates, modifies, or deletes a record in the Address Book tables (Address Book Master, F0101; Address Book - Who's Who, F0111; Contact Information, F01111; Address Book - Contact Phone Numbers F0115; Electronic Address, F01151; Address by Date, F0116).
RTABPHOUT2 is a single event that provides address book phone information within the RTABOUT2 container event. RTABPHOUT2 is generated only when RTABOUT2 is generated.
| Event Name | Event Description | Event Type | Event Category | Product Code | Data Structure | Event Relationship |
|---|---|---|---|---|---|---|
| RTABPHOUT2 | AB Phone Version 2 | RTE | Single | 01 | D0100100B: Address Book Master Phones Wrapper Data Structure | Included in container event RTABOUT. |
Conceptual Approach
An address book phone record added, modified, or deleted in the JD Edwards EnterpriseOne system creates, updates, or deletes a record in the Address Book - Contact Phone Numbers (F0115).
RTABEAOUT2 is a single event that provides address book email information within the RTABOUT2 container event. RTABEAOUT2 is generated only when RTABOUT2 is generated.
| Event Name | Event Description | Event Type | Event Category | Product Code | Data Structure | Event Relationship |
|---|---|---|---|---|---|---|
| RTABEAOUT2 | AB Electronic Address Version 2 | RTE | Single | 01 | D0100100C: Address Book Master Email Wrapper Data Structure | Included in container event RTABOUT. |
Conceptual Approach
An address book email record added, modified, or deleted in the JD Edwards EnterpriseOne system creates a new record in the Electronic Address (F01151) table.
RTPCOUT is a container event generated by the JD Edwards EnterpriseOne system to provide parent/child information to third-party systems.
| Event Type | Event Description | Event Category | Event Aggregate | Product Code |
|---|---|---|---|---|
| RTPCOUT | Parent Child Master | RTE | Container
Container event for:
|
H01 |
Objects that Can Initiate the Event
A parent child record added, changed, or deleted in the JD Edwards EnterpriseOne system creates, modifies, or deletes a record in the Address Organization Structure Master table (F0150) (Parent/Child table) This is the only event that initiates the container event, or any single events contained by this event.
RTPCOUTDS is a single event within the RTPCOUT container event that provides parent/child information to third-party systems. RTPCOUTDS is generated only when RTPCOUT is generated.
| Event Type | Event Description | Event Category | Event Aggregate | Product Code | Data Structure | Event Relationship |
|---|---|---|---|---|---|---|
| RTPCOUTDS | Parent Child Details | RTE | Single | H01 | D0100079A: ParentChild Master Manage Notify Real Time Structure | Included in container event RTPCOUT. |
RTPCOUT2 is a container event generated by the JD Edwards EnterpriseOne system to provide parent/child information to third-party systems.
| Event Type | Event Description | Event Category | Event Aggregate | Product Code |
|---|---|---|---|---|
| RTPCOUT2 | Parent Child Master Version 2 | RTE | Container
Container event for:
|
H01 |
Conceptual Approach
A parent child record added, changed, or deleted in the JD Edwards EnterpriseOne system creates, modifies, or deletes a record in the Address Organization Structure Master table (F0150) (Parent/Child table).
Objects that Can Initiate the Event
A parent child record added, changed, or deleted in the JD Edwards EnterpriseOne system creates, modifies, or deletes a record in the Address Organization Structure Master table (F0150) (Parent/Child table) This is the only event that initiates the container event, or any single events contained by this event.
RTPCOUTDS2 is a single event within the RTPCOUT2 container event that provides parent/child information to third-party systems. RTPCOUTDS2 is generated only when RTPCOUT2 is generated.
| Event Type | Event Description | Event Category | Event Aggregate | Product Code | Data Structure | Event Relationship |
|---|---|---|---|---|---|---|
| RTPCOUTDS2 | Parent Child Details Version 2 | RTE | Single | H01 | D0100102A: ParentChild Master Manage Notify Real Time Structure | Included in container event RTPCOUT. |
RTSHPOUT is a container event generated by the JD Edwards EnterpriseOne system to notify third-party systems about add or changes to the address book number of a branch plant record.
| Event Type | Event Description | Event Category | Event Aggregate | Product Code |
|---|---|---|---|---|
| RTSHPOUT | Branch Plant Address Book | RTE | Container
Container event for:
|
H42 |
Please see the appropriate real-time events that are contained by this event for information about the event fields associated with this event.
Conceptual Approach
An address book number added changed in a Branch Plant Constant table (F41001) in the JD Edwards EnterpriseOne system sends out ship to real-time events with address book (F0101), phones (F0115) and email (F01151) information. All phones and email are sent for the first contact only.
Objects that Can Initiate the Event
The P41001 - Branch Plant Constants program can initiate the RTSHPOUT event and all single events contained by the event.
RTSHPHDR is a single event that is generated by the JD Edwards EnterpriseOne system to provide ship to header information for a given branch plant.
| Event Type | Event Description | Event Category | Event Aggregate | Product Code | Data Structure | Event Relationship |
|---|---|---|---|---|---|---|
| RTSHPHDR | Branch Plant AB Header | RTE | Single | H41 | D4102160A: Ship To Real Time Header | Included in container event RTSHPOUT. |
Conceptual Approach
A ship to address book number added or modified in a branch plant modifies the Branch Plant Constants table and this information is sent out in a real-time event: Address Book Master (F0101).
RTSHPPHOUT is a single event generated by the JD Edwards EnterpriseOne system to provide address book phone information.
| Event Name | Event Description | Event Type | Event Category | Product Code | Data Structure | Event Relationship |
|---|---|---|---|---|---|---|
| RTSHPPHOUT | Branch Plant AB Phone | RTE | Single | H41 | D4102160B: Ship To Real Time Phones | Included in container event RTSHPOUT. |
Conceptual Approach
A ship to address book number added or modified in a branch plant modifies the Branch Plant Constants table and this information is sent out in a real-time event: all Address Book - Contact Phone Numbers (F0115) for the first contact.
RTSHPEAOUT is a single event generated by the JD Edwards EnterpriseOne system to provide address book email information.
| Event Type | Event Description | Event Category | Event Aggregate | Product Code | Data Structure | Event Relationship |
|---|---|---|---|---|---|---|
| RTSHPEAOUT | Branch Plant AB Elec Address | RTE | Single | H41 | D4102160C: Ship To Real Time Emails | Included in container event RTSHPOUT. |
Conceptual Approach
A ship to address book number added or modified in a branch plant modifies the Branch Plant Constants table and this information is sent out in a real-time event: all Electronic Address (F01151) records for the first contact.
You use batch import programs to import data from an external software system into the JD Edwards EnterpriseOne system, where it can then be processed by EnterpriseOne programs.
This table lists and describes the available batch import programs that are associated with the Address Book business object:
You use batch export programs to retrieve and format data from the JD Edwards EnterpriseOne database so that it can be used by an external software system.
| Program and Program Type | Description | Available Documentation |
|---|---|---|
| Initial Load of Address Book Geo Code program (R01120) | When you run the Initial Load of Address Book Geo Code (R01120) report, create or update the address book record, the system calls the business service, which communicates with Oracle Location Services to convert the address book record's address to a latitude and longitude and stores them in the Address Book Geo Code (F0119) table. | See this topic: |