Integration Guide Release: 11.0.1 Allocations alloc Allocations.jpg RMS publishes transfer and allocation messages; RCOM publishes customer order messages. Both of these are transformed by TAFRs to stock order messages, which are subscribed by RDM. Allocations are mainly used for Cross dock orders or to push merchandise out of the warehouse. Allocations Family Description: Functional Description: Family Diagram: 11.0 RMS Retek Merchandising System PUB etAllocFromRMSMFM cpToAndFromRMS etAllocFromRMS cpAlloc ewAllocFromRMS colAllocFromRMS crAllocFromRMS to_phys_loc, to_phys_loc_type RMSMFM_Alloc O_STATUS_CODE VARCHAR2 OUT, O_ERROR_MSG VARCHAR2 OUT, O_MESSAGE_TYPE VARCHAR2 OUT, O_MESSAGE RIB_OBJECT OUT, O_BUS_OBJ_ID RIB_BUSOBJID_TBL OUT, O_ROUTING_INFO RIB_ROUTINGINFO_TBL OUT, I_NUM_THREADS NUMBER IN DEFAULT, I_THREAD_VAL NUMBER IN DEFAULT 11.0, 10.1.9, 10.2 Allocations - Application: Process Name: Collaboration: Collaboration Rule: Subscriber Topic: Subscriber Connection: Publisher Topic: Publisher Connection: Durable Subscriber: Business Object ID: Routing Information: Transform Notes: Filter Notes: Routing Notes: General Comments: Message Type Object Name Retek Binding Mapping/Oracle Object Script Data Definition Name RIB Doc Type Name API Name: Parameters: Pub Hospital: Stagging Tables: Version: RIB_ALLOCDESC_REC,RIB_ALLOCDTLREF_REC,RIB_ALLOCDTLREF_TBL,RIB_ALLOCDTLTCKT_REC,RIB_ALLOCDTLTCKT_TBL,RIB_ALLOCDTL_REC,RIB_AL LOCDTL_TBL,RIB_ALLOCREF_REC CreateAllocRibObjects.sql allocdtldel AllocRef AllocRef RIB_ALLOCDESC_REC,RIB_ALLOCDTLREF_REC,RIB_ALLOCDTLREF_TBL,RIB_ALLOCDTLTCKT_REC,RIB_ALLOCDTLTCKT_TBL,RIB_ALLOCDTL_REC,RIB_AL LOCDTL_TBL,RIB_ALLOCREF_REC CreateAllocRibObjects.sql allocdtlmod AllocDesc AllocDesc RIB_ALLOCDESC_REC,RIB_ALLOCDTLREF_REC,RIB_ALLOCDTLREF_TBL,RIB_ALLOCDTLTCKT_REC,RIB_ALLOCDTLTCKT_TBL,RIB_ALLOCDTL_REC,RIB_AL allocdtlcre AllocDesc AllocDesc Thursday, October 28, 2004 Page 1 of 209 Retek® Integration Bus™ is a trademark of Retek Inc.
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Integration Guide Release: 11.0.1
Allocations alloc
Allocations.jpg
RMS publishes transfer and allocation messages; RCOM publishes customer order messages. Both of these are transformed by TAFRs to stock order messages, which are subscribedby RDM. Allocations are mainly used for Cross dock orders or to push merchandise out of the warehouse.
Thursday, October 28, 2004 Page 2 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
ASN Inbound asnin
ASN Inbound 10.3.jpg
ASN inbound messages are advanced shipment notification (ASN) messages that tell RDM to expect a shipment of merchandise. These messages can originate either from an outsidevendor (via EDI) or from another RDM instance (in the case of a transfer or allocation shipment). RMS subscribes to ASN inbound messages as well as RDM. RMS uses the ASN inboumessage to create shipment records.
Thursday, October 28, 2004 Page 3 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
RIB Retek Integration Bus
TAFR
etASNIn
cpASNIn
etASNInFromRIBToWH##
cpASNIn
ewASNInEDIToASNInLocFr colASNInEDIToASNInFromRIB
crASNInEDIToASNInFromRIB
facility_type, asn_type
colASNInEDIToASNInFromRIB
ASN Inbound-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:
This eway will ERROR out and shut down if the location ID on the line item of the order is not setup in RIB.Properties. If it is setup, it wadd an additional location instance to the end of the Topic name. i.e. WH1
Transform Notes:Filter Notes:
Routing Notes:
General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
ASNInRef.dtdasnindel ASNInRef ASNInRef
ASNInDesc.dtdasninmod ASNInDesc ASNInDesc
ASNInDesc.dtdasnincre ASNInDesc ASNInDesc
Thursday, October 28, 2004 Page 4 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
RWMS Retek Warehouse Distribution Management
PUB
etASNInFromRDMMFM
cpToAndFromRDMWH##
etASNIn
cpASNIn
ewASNInFromRDMWH## colASNInFromRDMWH##
crASNInFromRDM
RDMMFM_ASNIn
O_STATUS_CODE VARCHAR2 OUT, O_ERROR_MSG VARCHAR2 OUT, O_MESSAGE_TYPE VARCHAR2 OUT, O_MESSAGE RIB_OBJECT OUT, O_BUS_OBJ_ID RIB_BUSOBJID_TBLOUT, O_ROUTING_INFO RIB_ROUTINGINFO_TBL OUT, I_NUM_THREADS NUMBER IN DEFAULT, I_THREAD_VAL NUMBER IN DEFAULT, I_FACILITY_TYPE VARCHAR2 IN, I_DC_DEST_ID VARCHAR2 IN
Thursday, October 28, 2004 Page 7 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
RIB Retek Integration Bus
TAFR
etASNOut
cpASNOut
etASNInFromRIBToISO:etASNInFromRIBToWH##
cpASNIn
ewASNOutToASNInLocFro colASNOutToASNInLocFromRIB
crASNOutToASNInLocFromRIB
locType
locType=S | W
colASNOutToASNInLocFromRIB
ASN Inbound-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:Transform from ASNOut to ASNIn
This eway will ERROR out and shut down if the location ID on the ASN Out is not setup in RIB.Properties. If it is setup, it will add an additional location instance to the end of the Topic name. i.e. WH1
Transform Notes:Filter Notes:
Routing Notes:
General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
ASNInDesc.dtdasnincre ASNInDesc ASNInDesc
Thursday, October 28, 2004 Page 8 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
ASN Outbound asnout
ASN Outbound.jpg
RDM publishes advance shipment notification (ASN) messages that RMS uses to create or modify a shipment record. Any ASN that originates from RDM is called an "outbound" ASN. is also known as a bill of lading (BOL). An ASN that is coming into RDM is an "inbound" ASN.�Inbound ASNs can originate from external systems, or from another instance of RDM. Foexample, if an outbound shipment occurs because of a transfer to another warehouse, the outbound ASN is transformed into an inbound ASN and published to the receiving warehouse�Any outbound ASNs that originate because of a customer order are sent to RCOM, as well as to RMS. Shipments occurring because of a transfer or allocation are sent only to RMS.�
This is executed within the Subscriber MDB and never gets posted back to JMS.
colASNOutToASNOutCOFromRIB
com.retek.component.custo
Payload
11.0
ASN Outbound-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:
This eway only allows ASN Out messages that are related to Customer Orders. Additional ASN Out messages could be related to allocations and transfers. If consumer direct flag is NOT set to Y then it is dropped.
Transform Notes:Filter Notes:
Routing Notes:General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
asnoutdesc.dtdasnoutcre ASNOutDesc ASNOutDesc
Thursday, October 28, 2004 Page 12 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
RWMS Retek Warehouse Distribution Management
PUB
etRDMDBConn
cpToAndFromRDMWH##
etASNOut
cpASNOut
ewASNOutFromRDMWH## colASNOutFromRDMWH##
crASNOutFromRDM
RDMMFM_ASNOUT
O_STATUS_CODE VARCHAR2 OUT, O_ERROR_MSG VARCHAR2 OUT, O_MESSAGE_TYPE VARCHAR2 OUT, O_MESSAGE RIB_OBJECT OUT, O_BUS_OBJ_ID RIB_BUSOBJID_TBLOUT, O_ROUTING_INFO RIB_ROUTINGINFO_TBL OUT, I_NUM_THREADS NUMBER IN DEFAULT, I_THREAD_VAL NUMBER IN DEFAULT, I_FACILITY_TYPE VARCHAR2 IN, I_DC_DEST_ID VARCHAR2 IN
Thursday, October 28, 2004 Page 13 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
RIB Retek Integration Bus
TAFR
etASNOut
cpASNOut
etASNOutAT
cpASNOut
ewASNOutToASNOutATFro colASNOutToASNOutATFromRIB
crASNOutToASNOutATFromRIB
consumer_direct ,loc_type, facility_type
colASNOutToASNOutATFromRIB
RMSSUB_ASNOut
O_STATUS_CODE VARCHAR2 IN/OUT, O_ERROR_MESSAGE VARCHAR2 IN/OUT, I_MESSAGE RIB_OBJECT IN, I_MESSAGE_TYPE VARCHAR2 IN
RMS directly to RDM for this message, no TAFR required.
OUTBOUND_ASN_QUEUE
11.0, 10.1.9, 10.2
ASN Outbound-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:Drop all members of ASNOutDistroDesc array (in messageData) where consumer_direct is "Y"
If there is not at least one element of messageData.ASNOutDistrDesc array where consumer_direct is "N" or null, do not publish a etASNOutATFromRIB message
Transform Notes:Filter Notes:
Routing Notes:General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
ASNOutDesc.dtdasnoutcre ASNOutDesc ASNOutDesc
Thursday, October 28, 2004 Page 14 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
RMS Retek Merchandising System
SUB
etASNOutAT
cpASNOut
etRMSDBConn
cpToAndFromRMS
ewASNOutToRMS colASNOutToRMS
crASNOutToRMS
colASNOutToRMS
RMSSUB_ASNOut
O_STATUS_CODE VARCHAR2 IN/OUT, O_ERROR_MESSAGE VARCHAR2 IN/OUT, I_MESSAGE RIB_OBJECT IN, I_MESSAGE_TYPE VARCHAR2 IN
RMS directly to RDM for this message, no TAFR required.
Thursday, October 28, 2004 Page 15 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
Banner banner
Banners.jpg
RMS publishes messages about banners and channels to the RIB. A banner provides a means of grouping channels, thereby allowing the customer to link all brick and mortar stores, catalogs, and Web stores. The BANNER table holds a banner identifier and name. The CHANNELS table shows all channels and any associated banner identifiers. In order to take advantage of banners and channels, the customer must run RMS in a multi-channel environment.
Thursday, October 28, 2004 Page 17 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
Cost Zone Group costzngrp
Cost Zone Groups are published by RMS to an external system. The purpose of this is to enable any legacy system to use Cost zone groups so that they can either attach it to items orELC.
Cost Zone GroupFamily Description:Functional Description:Family Diagram:
11.0
RMS Retek Merchandising System
PUB
etCostZnGrpFromRMS
cpToAndFromRMS
etCostZnGrpFromRMS
cpCostZnGrp
ewCostZnGrpFromRMS colCostZnGrpFromRMS
crCostZnGrpFromRMS
RMSMFM_CostZnGrp
10.1.9, 10.2.2
Cost Zone Group-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:Transform Notes:
Filter Notes:Routing Notes:
General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
costzngrpmod CostZnGrpDesc CostZnGrp
costzncre CostZnGrpDesc CostZnGrp
costzngrploccre CostZnGrpDesc CostZnGrp
costzndel CostZnGrpRef CostZnGrpRef
costzngrplocmod CostZnGrpDesc CostZnGrp
costzngrpcre CostZnGrpDesc CostZnGrp
costzngrpdel CostZnGrpRef CostZnGrpRef
Thursday, October 28, 2004 Page 18 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
costznmod CostZnGrpDesc CostZnGrp
costzngrplocdel CostZnGrpRef CostZnGrpRef
Thursday, October 28, 2004 Page 19 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
Currency Rates currate
Currency Rates.jpg
Currency Rates from financials are published to RMS based on the exchange_type. RMS then decides whether to use the operational or consolidated or user-defined exchange types.
Thursday, October 28, 2004 Page 20 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
Customer Correspondence correspondence
The system needs to systematically create (real time) correspondence notifications based on pre-defined business rules and system events to send to the RIB. �RCOM will systematicpublish (real time) a message that contains order information for correspondences based on pre-defined business rules and system events (triggers). The business rules (that have beepreviously set up) will dictate the concept, correspondence type, correspondence template and what delivery method (email, hardcopy, etc.) will be used to send the correspondence tocustomer.
Thursday, October 28, 2004 Page 21 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
RCOM Retek Customer Order Management
SUB
etMediaFromExt
cpMedia
MediaToRCOM
PublishCorrespondenceRe
Payload
11.0
Customer Correspondence-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:Transform Notes:
Filter Notes:Routing Notes:
General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
custcorrescre CustCorresDesc CustCorresDesc
Thursday, October 28, 2004 Page 22 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
Customer Order Cost of Goods sold cogs
Cogs.jpg
Cost of goods sold information is published by RCOM to RMS for the intent of incrementing the inventory and decrementing the cost of goods sold at the virtual store in RMS for the itemThis message is subscribed by RMS from RCOM.�
Customer Order - Cost of Goods soldFamily Description:Functional Description:Family Diagram:
11.0
RCOM Retek Customer Order Management
PUB
etcogs
cpcogs
COCogsFromRCOM
PublishCostOfgoodsSoldRe
Payload
11.0
Customer Order Cost of Goods sold-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:Transform Notes:
Filter Notes:Routing Notes:
General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
cogscre CogsDesc CogsDesc
Thursday, October 28, 2004 Page 23 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
RMS Retek Merchandising System
SUB
etCOCogsFromRCOM
cpCOCogs
etRMSDBConn
cpToAndFromRMS
ewCOCogsToWSRMS colCOCogsToWSRMS
crCOCogsToWSRMS
PublishReturnLineCostOfGo
Payload
WS
Customer Order Cost of Goods sold-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:Transform Notes:
Filter Notes:Routing Notes:
General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
cogscre WSCogsDesc CogsDesc
cogscre WSCogsDesc CogsDesc
Thursday, October 28, 2004 Page 24 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
This uses a default TAFR implementation that allows you to filter message types that the applciation does not want. The property is tafr.types.filter.[familyName] = [Valid Message types]
com.retek.component.custo
Payload
11.0
Customer Return-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:Transform Notes:
Filter Notes:Routing Notes:
General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
coretcre CustRetDesc CustRetDesc
Thursday, October 28, 2004 Page 26 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
RCOM Retek Customer Order Management
SUB
etCustReturn
cpCustReturn
CustReturnToRCOM
com.retek.component.custo
Payload
11.0
Customer Return-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:Transform Notes:
Filter Notes:Routing Notes:
General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
coretcre CustRetDesc CustRetDesc
Thursday, October 28, 2004 Page 27 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
RWMS Retek Warehouse Distribution Management
PUB
etCustReturnFromRDMMFM
cpToAndFromRDMWH##
etCustReturn
cpCustReturn
ewCustReturnFromRDMWH colCustReturnFromRDMWH##
crCustReturnFromRDM
RDMMFM_CustReturn
O_STATUS_CODE VARCHAR2 OUT, O_ERROR_MSG VARCHAR2 OUT, O_MESSAGE_TYPE VARCHAR2 OUT, O_MESSAGE RIB_OBJECT OUT, O_BUS_OBJ_ID RIB_BUSOBJID_TBLOUT, O_ROUTING_INFO RIB_ROUTINGINFO_TBL OUT, I_NUM_THREADS NUMBER IN DEFAULT, I_THREAD_VAL NUMBER IN DEFAULT, I_FACILITY_TYPE VARCHAR2 IN, I_DC_DEST_ID VARCHAR2 IN
Thursday, October 28, 2004 Page 28 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
Customer Return Sale coreturn
Cust Return Sale.jpg
When RCOM receives a return of a customer order sale, it publishes a customer order return sale message to the RIB for RMS. RMS will update the inventory at the virtual store and aincrement the inventory at the WH location.
Thursday, October 28, 2004 Page 30 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
Customer Sale cosale
Cust Sale.jpg
Whenever RCOM receives a notification from RDM that a customer order has been shipped (an ASNOut message), it publishes a Customer Order Sale message to RMS.
Thursday, October 28, 2004 Page 32 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
Differentiator Groups diffgrp
Differentiator Groups.jpg
Differentiator groups allow clients to group differentiator identifiers (Diff IDs) into logical groupings, for example, pant sizes, shirt colors, or flavors. RMS publishes differentiator group messages to the RIB. RCOM and RDM subscribe to these messages. There are header and detail messages. A diff group header is the diff group itself, and the details are individual dIDs. See "Differentiator identifiers" in the preceding section for more information.
This uses a default TAFR implementation that allows you to filter message types that the applciation does not want. The property is tafr.types.filter.[familyName] = [Valid Message types]
com.retek.component.item.i
Payload
11.0
Differentiator Groups-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:
Filters out messages not listed in the properties file. No deletes are excepted.
Transform Notes:Filter Notes:
Routing Notes:General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
diffgrphdrcre DiffGrpHdrDesc DiffGrpHdrDesc
diffgrpdtlmod DiffGrpDtlDesc DiffGrpDtlDesc
diffgrpdtlcre DiffGrpDtlDesc DiffGrpDtlDesc
diffgrphdrmod DiffGrpHdrDesc DiffGrpHdrDesc
Thursday, October 28, 2004 Page 33 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
RCOM Retek Customer Order Management
SUB
etDiffGrp
cpDiffGrp
DiffGrpToRCOM
com.retek.component.item.i
Payload
11.0
Differentiator Groups-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:Transform Notes:
Filter Notes:Routing Notes:
General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
diffgrphdrcre DiffGrpHdrDesc DiffGrpHdrDesc
diffgrpdtlmod DiffGrpDtlDesc DiffGrpDtlDesc
diffgrpdtlcre DiffGrpDtlDesc DiffGrpDtlDesc
diffgrphdrmod DiffGrpHdrDesc DiffGrpHdrDesc
Thursday, October 28, 2004 Page 34 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Thursday, October 28, 2004 Page 35 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
RWMS Retek Warehouse Distribution Management
SUB
etDiffGrpFromRMS
cpDiffGrp
etDiffGrpRDMAPIWH##
cpToAndFromRDMWH##
ewDiffGrpToRDMWH## colDiffGrpToRDMWH##
crDiffGrpToRDM
colDiffGrpToRDMWH##
RDMSUB_DiffGrp
O_STATUS_CODE VARCHAR2 OUT, O_ERROR_MSG VARCHAR2 OUT, O_MESSAGE_TYPE VARCHAR2 OUT, O_MESSAGE RIB_OBJECT OUT, O_BUS_OBJ_ID RIB_BUSOBJID_TBLOUT, O_ROUTING_INFO RIB_ROUTINGINFO_TBL OUT, I_NUM_THREADS NUMBER IN DEFAULT, I_THREAD_VAL NUMBER IN DEFAULT, I_FACILITY_TYPE VARCHAR2 IN, I_DC_DEST_ID VARCHAR2 IN1�Because differentiator groups are foundation data, the RIB does not route these messages by warehouse ID. All RDM instances receive the same message.�2�Note that RDM does not usthe DiffGrpDtlMod message, nor does it have a subscribing API for it. The ewDiffGrpToRDMWH## e*Way ignores any DiffGrpDtlMod message it encounters.�
10.3
Differentiator Groups-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:Transform Notes:
Filter Notes:Routing Notes:
General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
RIB_DiffGrpHdrDesc_RECCreateDiffGrpRibObjects.sql
diffgrphdrmod DiffGrpHdrDesc DiffGrpHdrDesc
RIB_DiffGrpRef_RECCreateDiffGrpRibObjects.sql
diffgrpdel DiffGrpRef DiffGrpRef
RIB_DiffGrpDtlDesc_RECCreateDiffGrpRibObjects.sql
diffgrpdtlcre DiffGrpDtlDesc DiffGrpDtlDesc
RIB_DiffGrpDtlRef_RECCreateDiffGrpRibObjects.sql
diffgrpdtldel DiffGrpDtlRef DiffGrpDtlRef
RIB_DiffGrpHdrDesc_RECCreateDiffGrpRibObjects.sql
diffgrphdrcre DiffGrpHdrDesc DiffGrpHdrDesc
Thursday, October 28, 2004 Page 36 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
Differentiators diffs
Differentiators.jpg
Differentiators ("Diffs" as they are commonly called) allow users to further distinguish items. RMS publishes these differentiators as messages to the RIB. RCOM and RDM both subscrto Diff messages.
This uses a default TAFR implementation that allows you to filter message types that the applciation does not want. The property is tafr.types.filter.[familyName] = [Valid Message types]
com.retek.component.item.i
Payload
11.0
Differentiators-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:
Filters out messages not listed in the properties file. No deletes are excepted.
Transform Notes:Filter Notes:
Routing Notes:General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
diffmod DiffDesc DiffDesc
diffcre DiffDesc DiffDesc
Thursday, October 28, 2004 Page 37 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Thursday, October 28, 2004 Page 40 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
RWMS Retek Warehouse Distribution Management
SUB
etDiffsFromRMS
cpDiffs
etDiffsRDMAPIWH##
cpToAndFromRDMWH##
ewDiffsToRDMWH## colDiffsToRDMWH##
crDiffsToRDM
colDiffsToRDMWH##
RDMSUB_Diffs
O_STATUS_CODE VARCHAR2 OUT, O_ERROR_MSG VARCHAR2 OUT, O_MESSAGE_TYPE VARCHAR2 OUT, O_MESSAGE RIB_OBJECT OUT, O_BUS_OBJ_ID RIB_BUSOBJID_TBLOUT, O_ROUTING_INFO RIB_ROUTINGINFO_TBL OUT, I_NUM_THREADS NUMBER IN DEFAULT, I_THREAD_VAL NUMBER IN DEFAULT, I_FACILITY_TYPE VARCHAR2 IN, I_DC_DEST_ID VARCHAR2 INBecause differentiators are foundation data, the RIB does not route these messages by warehouse ID. All RDM instances receive the same message.
10.3
Differentiators-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:Transform Notes:
Filter Notes:Routing Notes:
General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
RIB_DiffDesc_RECCreateDiffsRibObjects.sql
diffcre DiffDesc DiffDesc
RIB_DiffDesc_RECCreateDiffsRibObjects.sql
diffmod DiffDesc DiffDesc
RIB_DiffRef_RECCreateDiffsRibObjects.sql
diffdel DiffRef DiffRef
Thursday, October 28, 2004 Page 41 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
Direct Ship Receipt dsrcpt
Direct Ship Receipt.jpg
This message brings all the shipments occuring at a 3rd party location to RMS via RCOM. The message will update the inventory at virtual store by +1 unit and then the POSUPLD will decrement the inventory of a sale by -1 and thus net inventory remains zero. This message is subscribed by RMS from RCOM.
Direct ship confirmation from a 3rd party to RMS via RCOM. Family Description:Functional Description:Family Diagram:
11.0
RCOM Retek Customer Order Management
PUB
etdsrcpt
cpdsrcpt
CODSRcptFromRCOM
PublishDSRcptRemoteCom
Payload
11.0
Direct Ship Receipt-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:Transform Notes:
Filter Notes:Routing Notes:
General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
dsrcptcre DSRcptDesc DSRcptDesc
Thursday, October 28, 2004 Page 42 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
RMS Retek Merchandising System
SUB
etDSRCPT
cpDSRCPT
etDSRCPT
cpDSRCPT
ewDSRCPTToRMS colDSRCPTToRMS
crDSRCPTToRMS
RMSSUB_DSRCPT
11.0
Direct Ship Receipt-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:Transform Notes:
Filter Notes:Routing Notes:
General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
dsrcptdesc.dtddsrcptcre DSRcptDesc DSRcptDesc
Thursday, October 28, 2004 Page 43 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
DSD Receipt dsdreceipt
DSD Receipts.jpg
DSD receipts pertain to Purchase order receipts at the store. Once a PO is received at the store the DSS receipt message brings the receipt information to RMS.
Thursday, October 28, 2004 Page 46 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
Emp emp
Employee 10.3.jpg
The Labor Management System (LMS) is a tool to provide users with the capability to improve labor efficiency, reduce labor cost, improve equipment and building capacity utilization, improve customer service, and increase profitability by providing the user with critical performance information and analytics required to manage and optimize logistics operations. LMSstandards based system, allowing the user to develop a time standard for every process performed in the operation and compare actual process time to standard time to calculate productivity and performance for every measured function. LMS provides reports that provide management visibility on productivity and performance for every activity, employee, department, and building over a timeframe defined by the user, enabling management to identify problem areas requiring improvement. LMS can be interfaced with RDM or an existing WMS, and can be linked to time and attendance systems for employee and time information.
Thursday, October 28, 2004 Page 47 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
EmpTime emptime
Emp Time 10.3.jpg
The Labor Management System (LMS) is a tool to provide users with the capability to improve labor efficiency, reduce labor cost, improve equipment and building capacity utilization, improve customer service, and increase profitability by providing the user with critical performance information and analytics required to manage and optimize logistics operations. LMSstandards based system, allowing the user to develop a time standard for every process performed in the operation and compare actual process time to standard time to calculate productivity and performance for every measured function. LMS provides reports that provide management visibility on productivity and performance for every activity, employee, department, and building over a timeframe defined by the user, enabling management to identify problem areas requiring improvement. LMS can be interfaced with RDM or an existing WMS, and can be linked to time and attendance systems for employee and time information.
Employee Time From Time ApplicationFamily Description:Functional Description:
Family Diagram:
11.0
RLM Retek Labor Management
SUB
etEXTEmpTime
cpEmpTime
etEmpTimeRLMAPI
cpToAndFromRLM
ewEmpTimeToRLM colEmpTimeToRLM
crEmpTimeToRLM
crEmpTimeToRLM
RLMSUB_EmpTime
O_STATUS_CODE VARCHAR2 OUT, O_ERROR_MESSAGE VARCHAR2 OUT, I_MESSAGE RIB_OBJECT IN, I_MESSAGE_TYPE VARCHAR2 IN, I_FACILITY_TYPE VARCHAR2 IN
10.3
EmpTime-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:Transform Notes:
Filter Notes:Routing Notes:
General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
EmpTimeDesc.dtdEmpTimeCre EmpTimeDesc EmpTimeDesc
Thursday, October 28, 2004 Page 48 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
Freight Terms frtterm
Freight Terms.jpg
Freight Terms from external financial applications published to RMS to identify various terms condition based on the freight associated to a supplier. Freight Terms are created in externfinancial applications as a separate entity and then it gets associated to a supplier when a new supplier is created.
Thursday, October 28, 2004 Page 49 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
Gift Registry giftregGift Registry Acknowledgement and UpdatesFamily Description:
Functional Description:Family Diagram:
11.0
RCOM Retek Customer Order Management
PUB
etGiftReg
cpGiftReg
GiftRegFromRCOM
PublishGiftRegRemoteCom
Payload
11.0
Gift Registry-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:Transform Notes:
Filter Notes:Routing Notes:
General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
giftregupdmod GiftRegUpdDesc GiftRegUpdDesc
giftregackcre GiftRegAckDesc GiftRegAckDesc
Thursday, October 28, 2004 Page 50 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
GL Chart of Accounts glcoa
GL Chart of Accounts.jpg
GL Chart of Accounts defines the accounting structure in any financial applications. As the financial application determines the final payment, it is necessary to bring over the account information to RMS and ReSA in order to send the Stock information of RMS and Total IDs of ReSA back to Financials. As the accounting structure in financials always do not match thaccounting structure in RMS and ReSA, it is necessary to map the financial accounting structure to RMS Merchandise hierarchy and ReSA's Total ID. This mapping would facilitate the matching of the accounts on both sides of the application and the journal entries in financials.
GL Chart of AccountsFamily Description:Functional Description:
Family Diagram:
11.0
RMS Retek Merchandising System
SUB
etEXTGLCOA
cpEXTGLCOA
etGLCOARMSAPI
cpToAndFromRMS
ewGLCOAToRMS colGLCOAToRMS
crGLCOAToRMS
colGLCOAToRMS
RMSSUB_GLCOA
11.0, 10.1.9, 10.2
GL Chart of Accounts-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:Transform Notes:
Filter Notes:Routing Notes:
General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
glcoacre GLCOADesc GLCOADesc
Thursday, October 28, 2004 Page 51 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
Inventory Adjustments invadjust
Inv Adjust.jpg
RDM publishes inventory adjustment data in messages to the RIB. The data in the messages includes disposition codes for quantities of items for one location. RMS subscribes to thesmessages in order to:��Adjust overall quantities of stock on hand for an item at a location�Adjust the availability of item-location quantities��RDM sends messages that may contain values in the from_disposition and to_disposition XML tags. RMS only processes disposition changes that may alter an item's inventory status between available or unavailable In additif either the from_disposition or the to_disposition is null, RMS treats this fact as an addition or subtraction to overall stock on hand for the item.�
Thursday, October 28, 2004 Page 55 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
Inventory Request invreq
Inv Req.jpg
This interface allows for ISO to send a store need quantity to the host system. RMS generates a transfer or creates a PO (for the requesting store) based on replenishment parametersup in RMS.
This uses a default TAFR implementation that allows you to filter message types that the applciation does not want. The property is tafr.types.filter.[familyName] = [Valid Message types]
com.retek.component.item.i
Payload
11.0
ItemLoc-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:
Filters out messages not listed in the properties file
Transform Notes:Filter Notes:
Routing Notes:General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
itemlocmod ItemLocDesc ItemLocDesc
itemloccre ItemLocDesc ItemLocDesc
Thursday, October 28, 2004 Page 62 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Thursday, October 28, 2004 Page 64 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
RMSWS Retek Merchandising System(WS)
PUB
etItemsFromWSRMSMFM
cpToAndFromRMS
etItemsFromRMS
cpItems
ewItemsFromWSRMS colItemsFromWSRMS
crItemsFromWSRMS
RMSMFM_WSI_ITEM
O_status_code OUT VARCHAR2, O_error_msg OUT VARCHAR2,O_message_type OUT VARCHAR2, O_message IN OUT CLOB, O_item OUT WSI_ITEM_MFQUEUE.ITEM%TYPE, I_num_threads IN NUMBER DEFAULT 1, I_thread_val IN NUMBER DEFAULT 1
WS
ItemLoc-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:Transform Notes:
Filter Notes:Routing Notes:
General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
itemlocmod ItemLocDesc ItemLocDesc
itemloccre ItemLocDesc ItemLocDesc
Thursday, October 28, 2004 Page 65 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
SIM Store Inventory Management
SUB
etItemLocISO
cpItemLoc
ItemLocMessagingCompone
etItemLocISO
com.chelseasystems.cs.dat
10.4
ItemLoc-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:Transform Notes:
Filter Notes:Routing Notes:
General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
itemlocreplmod ItemLocDesc ItemLocDesc
itemlocdel ItemLocRef ItemLocRef
Thursday, October 28, 2004 Page 66 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
RCOM Retek Customer Order Management
SUB
etItemLoc
cpItemLoc
ItemLocToRCOM
com.retek.component.item.i
Payload
11.0
ItemLoc-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:Transform Notes:
Filter Notes:Routing Notes:
General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
itemloccre ItemLocDesc ItemLocDesc
itemloccre ItemLocDesc ItemLocDesc
itemlocmod ItemLocDesc ItemLocDesc
itemlocmod ItemLocDesc ItemLocDesc
Thursday, October 28, 2004 Page 67 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
Items items
Items.jpg
RMS publishes item data to the RIB. All sellable items are subscribed to by both RDM and RCOM. However, non-sellable items (like non-sellable packs) only go to RDM.��Before an ican be successfully consumed by a subscribing application, the vendor, location, UDAs, diffs, channels or banners that the item references must have already been successfully consuby the same subscribing application.�
Thursday, October 28, 2004 Page 69 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
ISCDimDesc.dtdiscdimmod ISCDimDesc ISCDimDesc
ISCDimDesc.dtdiscdimcre ISCDimDesc ISCDimDesc
ItemBOMRef.dtditembomdel ItemBOMRef ItemBOMRef
ItemBOMDesc.dtditembomcre ItemBOMDesc ItemBOMDesc
ItemBOMDesc.dtditembommod ItemBOMDesc ItemBOMDesc
ItemRef.dtditemdel ItemRef ItemRef
ItemDesc.dtditemcre ItemDesc ItemDesc
RIB Retek Integration Bus
TAFR
etItemsFromRMS
cpItems
etItemsISO
cpItems
ewItemsToItemsISOFromRI colItemsToItemsISOFromRIB
crItemsToItemsISOFromRIB
colItemsToItemsISOFromRIB
Item ID
Items-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:
The following message types are not used by the ISO application. iscdimcre,iscdimdel,iscdimmod,itemudalovcre,itemudalovmod,itemudalovdel,itemudaffcre,itemudaffmod,itemudaffdel,itemudadatecre,itudadatemod,itemudadatedel,itemimagecre,itemimagemod,itemimagedel
Transform Notes:Filter Notes:
Routing Notes:General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
ItemUPCDesc.dtditemupccre ItemUPCDesc ItemUPCDesc
Thursday, October 28, 2004 Page 70 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Thursday, October 28, 2004 Page 78 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
ItemWH itemwh
ItemWH 10.3.jpg
Items will be published to the RIB via the Publish Item Data menu object within RDM. The third party system determines how the items will be inserted based on import logic built into itsystem.
Thursday, October 28, 2004 Page 81 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
Locations loc
Locations 10.3.jpg
For Retek 10 Integration Bus purposes, the word "locations" can apply to: Stores and warehouses in RMS; Virtual stores and warehouses in RCOM�* Ship methods in RCOM�* Physlocations in RDM��RMS publishes stores and warehouses (both physical and virtual) to the RIB using the e*Ways:�* ewStoresFromRMS�* ewWHFromRMS ��RCOM publishes shmethods to the RIB using the e*Way:�* ewShipMethFromRCOM��RCOM subscribes to virtual stores and warehouses, and RDM subscribes to locations. In a multi-channel environmbefore a location can be successfully consumed by the subscribing application, any channels or banners that the location references must have already been successfully consumed bysame subscribing application.�
This eway will create one message that is etLocationFromRIB (These messages only contain physical Warehouses) and one etStoresFromRIB (These messages only contain vitual messages)
colStoresToLocationFromRIB
Store ID, Location ID
RDMSUB_Loc
O_STATUS_CODE VARCHAR2 OUT, O_ERROR_MSG VARCHAR2 OUT, O_MESSAGE_TYPE VARCHAR2 OUT, O_MESSAGE RIB_OBJECT OUT, O_BUS_OBJ_ID RIB_BUSOBJID_TBLOUT, O_ROUTING_INFO RIB_ROUTINGINFO_TBL OUT, I_NUM_THREADS NUMBER IN DEFAULT, I_THREAD_VAL NUMBER IN DEFAULT, I_FACILITY_TYPE VARCHAR2 IN, I_DC_DEST_ID VARCHAR2 IN
10.3
Locations-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:This eway transforms Stores to a location message. No contents of the message are actually changed. Format only.Transform Notes:
Thursday, October 28, 2004 Page 83 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
RIB Retek Integration Bus
TAFR
etWHFromRMS
cpWH
etLocationsFromRIB:etWHFromRIB
cpLocations:cpWH
ewWHToLocationsFrom RIB colWHToLocationsFrom RIB
crWHToLocationsFrom RIB
Location_type
This eway will create one message that is etLocationFromRIB (These messages only contain physical Warehouses) and one etStoresFromRIB (These messages only contain vitual messages)
colWHToLocationsFrom RIB
Warehouse ID, Location ID
Locations-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:This eway transforms messages from a warehouse format to a location formatted messageTransform Notes:
Thursday, October 28, 2004 Page 87 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
Organization Hierarchy orghier
The organization hierarchy message provides data about the relationships between the company, chain, area, region, district, store, etc of the company.
Thursday, October 28, 2004 Page 88 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
Partner partner
Partner.jpg
Partners are set up in RMS as a bank, agent, distributor, external finisher etc. Partners are transformed into locations in the RIB. Partners are mainly used as External finishers while performing transfers.
O_STATUS_CODE OUT VARCHAR2, O_ERROR_MSG OUT VARCHAR2, O_MESSAGE OUT RIB_OBJECT, O_MESSAGE_TYPE IN/OUT VARCHAR2, O_BUS_OBJ_ID IN/OUT NOCOPY RIB_BISOBJID_TBL, O_ROUTING_INFO IN/OUT NOCOPY RIB_ROUTINGINFO_TBL
RIB_MESSA
11.0, 10.1.9, 10.2
Partner-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:Transform Notes:
Filter Notes:Routing Notes:
General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
partnerdtlcre PartnerDesc PartnerDesc
partnermod PartnerDesc PartnerDesc
partnerdtlmod PartnerDesc PartnerDesc
partnercre PartnerDesc PartnerDesc
partnerdel PartnerRef PartnerRef
partnerdtldel PartnerRef PartnerRef
Thursday, October 28, 2004 Page 89 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
Payment Terms payterm
Pay Terms.jpg
Payment Terms from external financial applications are published to RMS to identify various payment conditions associated to a supplier. Payment Terms are created in external financapplications as a separate entity and then it gets associated to a supplier when a new supplier is created.
Thursday, October 28, 2004 Page 90 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
Payments paymentsPaymentsFamily Description:
Functional Description:Family Diagram:
11.0.1
RCOM Retek Customer Order Management
PUB
etPayments
cpPayments
PaymentsFromRCOM
PublishPaymentsRemoteCo
Payload
11.0
Payments-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:Transform Notes:
Filter Notes:Routing Notes:
General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
RefdPayStlmtCre RefdPayStlmtDesc RefdPayStlmtDesc
Thursday, October 28, 2004 Page 91 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
Pending Return pendreturn
Pending Return 10.3.jpg
RCOM publishes a pending return message to RDM whenever it has been notified that a customer order will be returned. After the return arrives, RDM publishes a customer return message for RCOM.
Thursday, October 28, 2004 Page 93 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
PrcChgConf prcchgconf
RMS replies to SIM's Price Change Request (PrcChgReq) witha Price Change Confirmation. This message contains a status notifying SIM whether or not the price change will be put effect.
Thursday, October 28, 2004 Page 95 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
SIM Store Inventory Management
PUB
etPrcChgReq
cpPrcChgReq
PrcChgReqPublisher.cfg
etPrcChgReq
com.chelseasystems.cs.dat
10.4
PrcChgReq-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:Transform Notes:
Filter Notes:Routing Notes:
General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
prcchgreqcre PrcChgReqDesc PrcChgReqDesc
Thursday, October 28, 2004 Page 96 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
Price Zone Group prczonegrp
This interface takes all the price zone group store information from RMS to ISO. The purpose is for store system to be able to view all store/zone relationships.
Price Zone GroupFamily Description:Functional Description:Family Diagram:
Thursday, October 28, 2004 Page 97 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
Purchase Order order
Purchase Orders.jpg
Purchase order messages may pertain to physical locations only, or to virtual or physical locations. This section describes message publication and subscription for both situations. ��Physical location purchase order data��RMS publishes purchase order data for physical locations to the RIB, using the ewOrderPhysFromRMS adapter (e*Way). When the data is originally at the virtual location level, RMS rolls it up to the physical location level before writing it to the physical order message queue table. This process results from the fact that RDMthe only subscriber for purchase orders, accepts data only at the physical location level. �Virtual location purchase order data ��RMS also publishes purchase order data for virtual anphysical locations, using the ewOrderFromRMS adapter. This adapter can publish either virtual or physical location data, depending on how RMS is configured.
This uses a default TAFR implementation that allows you to filter message types that the applciation does not want. The property is tafr.types.filter.[familyName] = [Valid Message types]
com.retek.component.custo
Payload
11.0
Purchase Order-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:
Filters out messages not listed in the properties file
Transform Notes:Filter Notes:
Routing Notes:General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
podtlcre PODesc PODesc
podel PORef PORef
podtlmod PODesc PODesc
Thursday, October 28, 2004 Page 98 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
RMS Retek Merchandising System
PUB
etOrderFromRMSMFM
cpToAndFromRMS
etOrderFromRMS
cpOrder
ewOrderFromRMS colOrderFromRMS
crOrderFromRMS
to_phys_loc, to_phys_loc_type
RMSMFM_Order
O_STATUS_CODE VARCHAR2 OUT, O_ERROR_MSG VARCHAR2 OUT, O_MESSAGE_TYPE VARCHAR2 OUT, O_MESSAGE RIB_OBJECT OUT, O_BUS_OBJ_ID RIB_BUSOBJID_TBLOUT, O_ROUTING_INFO RIB_ROUTINGINFO_TBL OUT, I_NUM_THREADS NUMBER IN DEFAULT, I_THREAD_VAL NUMBER IN DEFAULTMany events in the RMS purchase order creation or modification process write a row to the ORDER_MFQUEUE table. For example, there may be many rows in the queue table, but they may represent only a few POPhysCre messages. The message family manager combines the rows on the queue table into one message to publish to the RIB.
Thursday, October 28, 2004 Page 100 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
PORef.dtdpodel PORef PORef
PODtlRef.dtdpodtldel PORef PORef
PODesc.dtdpocre PODesc PODesc
POHdrDesc.dtdpohdrmod PODesc PODesc
PODtlDesc.dtdpodtlmod PODesc PODesc
RIB Retek Integration Bus
TAFR
etOrderFromRMS
cpOrder
etOrderFromRIBToWH##
cpOrder
ewOrderToOrderWHFromRI colOrderToOrderWHFromRIB
crOrderToOrderWHFromRIB
facility_type, to_phys_loc_type
colOrderToOrderWHFromRIB
Order Id, Order ID plus Location ID
RDMSUB_Order
O_STATUS_CODE VARCHAR2 OUT, O_ERROR_MSG VARCHAR2 OUT, O_MESSAGE_TYPE VARCHAR2 OUT, O_MESSAGE RIB_OBJECT OUT, O_BUS_OBJ_ID RIB_BUSOBJID_TBLOUT, O_ROUTING_INFO RIB_ROUTINGINFO_TBL OUT, I_NUM_THREADS NUMBER IN DEFAULT, I_THREAD_VAL NUMBER IN DEFAULT, I_FACILITY_TYPE VARCHAR2 IN, I_DC_DEST_ID VARCHAR2 IN
10.3
Purchase Order-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:
This eway will only include line items that are relevant to the location that the message is being routed to.
This eway will ERROR out and shut down if the location ID on the line item of the order is not setup in RIB.Properties. If it is setup, it wadd an additional location instance to the end of the Topic name. i.e. WH1
Transform Notes:Filter Notes:
Routing Notes:
General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
pohdrmod PODesc PODesc
podtlmod PODesc PODesc
pocre PODesc PODesc
podel PORef PORef
Thursday, October 28, 2004 Page 101 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
podtldel PORef PORef
podtlcre PODesc PODesc
PODtlCreDesc.dtdpodtlcre PODesc PODesc
PORef.dtdpodel PORef PORef
PODtlRef.dtdpodtldel PORef PORef
PODesc.dtdpocre PODesc PODesc
POHdrDesc.dtdpohdrmod PODesc PODesc
PODtlDesc.dtdpodtlmod PODesc PODesc
RWMS Retek Warehouse Distribution Management
SUB
etOrderFromRIBToWH##
cpOrder
etRDMDBConn
cpToAndFromRDMWH##
ewOrderToRDMWH## colOrderToRDMWH##
crOrderToRDM
colOrderToRDMWH##
RDMSUB_Order
O_STATUS_CODE VARCHAR2 OUT, O_ERROR_MSG VARCHAR2 OUT, O_MESSAGE_TYPE VARCHAR2 OUT, O_MESSAGE RIB_OBJECT OUT, O_BUS_OBJ_ID RIB_BUSOBJID_TBLOUT, O_ROUTING_INFO RIB_ROUTINGINFO_TBL OUT, I_NUM_THREADS NUMBER IN DEFAULT, I_THREAD_VAL NUMBER IN DEFAULT, I_FACILITY_TYPE VARCHAR2 IN, I_DC_DEST_ID VARCHAR2 IN
10.3
Purchase Order-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:Transform Notes:
Filter Notes:Routing Notes:
General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
Thursday, October 28, 2004 Page 102 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
RIB_PODESC_RECCreatePORibObjects.sql
pohdrmod PODesc PODesc
RIB_POREF_RECCreatePORibObjects.sql
podel PORef PORef
RIB_POREF_RECCreatePORibObjects.sql
podtldel PORef PORef
RIB_PODESC_RECCreatePORibObjects.sql
pocre PODesc PODesc
RIB_PODESC_RECCreatePORibObjects.sql
podtlcre PODesc PODesc
RIB_PODESC_RECCreatePORibObjects.sql
podtlmod PODesc PODesc
Thursday, October 28, 2004 Page 103 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Thursday, October 28, 2004 Page 104 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
com/retek/binding/rib/payload/PODescMap.xml
RCOM Retek Customer Order Management
SUB
etOrder
cpOrder
OrderToRCOM
com.retek.component.custo
Payload
11.0
Purchase Order-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:Transform Notes:
Filter Notes:Routing Notes:
General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
podtlcre PODesc PODesc
Thursday, October 28, 2004 Page 105 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
Purchase Order WS order
Purchase Orders 10.3.jpg
Purchase order messages may pertain to physical locations only, or to virtual or physical locations. This section describes message publication and subscription for both situations. ��Physical location purchase order data��RMS publishes purchase order data for physical locations to the RIB, using the ewOrderPhysFromRMS adapter (e*Way). When the data is originally at the virtual location level, RMS rolls it up to the physical location level before writing it to the physical order message queue table. This process results from the fact that RDMthe only subscriber for purchase orders, accepts data only at the physical location level. �Virtual location purchase order data ��RMS also publishes purchase order data for virtual anphysical locations, using the ewOrderFromRMS adapter. This adapter can publish either virtual or physical location data, depending on how RMS is configured.
Purchase Order WSFamily Description:Functional Description:
Family Diagram:
WS
RCOM Retek Customer Order Management
SUB
etOrder
cpOrder
OrderToRCOM
com.retek.component.custo
Payload
11.0
Purchase Order WS-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:Transform Notes:
Filter Notes:Routing Notes:
General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
podtlmod PODesc PODesc
podel PORef PORef
Thursday, October 28, 2004 Page 106 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
Receiver Unit Adjustment rcvunitadj
Rcvr Unit Adj.jpg
In order to be able to correct the mistakes and make the functionality work for wrong receipt or over/under receipt, new functionality of Receiver Unit Adjustment is used. This is a publisout of RMS and is typically used for sending adjustments to warehousing and Store systems.
Receiver Unit AdjustmentFamily Description:Functional Description:Family Diagram:
11.0
RMS Retek Merchandising System
PUB
etRcvUnitAdj
cpRcvUnitAdj
etRcvUnitAdj
cpRcvUnitAdj
ewRcvUnitAdjFromRMS colRcvUnitAdjFromRMS
crRcvUnitAdjFromRMS
RMSMFM_RcvUnitAdj
O_STATUS_CODE VARCHAR2, O_ERROR_MSG VARCHAR2, O_MESSAGE_TYPE IN/OUT VARCHAR2, O_MESSAGE OUT RIB_OBJECT, O_BUS_OBJ_ID IN/OUT RIB_BUSOBJID_TBLO_ROUTING_INFO IN/OUT RIB_ROUTINGINFO_TBL, I_REF_OBJECT IN RIB_OBJECT
Thursday, October 28, 2004 Page 107 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
SIM Store Inventory Management
SUB
etRcvUnitAdj
cpRcvUnitAdj
RcvUnitAdjmessagingcomp
com.chelseasystems.cs.dat
10.4
Receiver Unit Adjustment-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:Transform Notes:
Filter Notes:Routing Notes:
General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
rcvunitadjcre RcvUnitAdjDesc RcvUnitAdjDesc
Thursday, October 28, 2004 Page 108 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
Receiving receiving
Receiving.jpg
Receiving consists of appointment and receipt messages that RDM publishes to the RIB for RMS. An appointment is information about the arrival of merchandise at a location. A receipmessage tells RMS when merchandise arrives in RDM. It also allows RMS to close the appointment for that receipt
Thursday, October 28, 2004 Page 113 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
Regular Price Changes regprcchg
Approved regular price changes are sent over from RPM to RMS for Ticketing purposes.
Approved Regular price changes originating in RPMFamily Description:Functional Description:Family Diagram:
11.0.1
RMS Retek Merchandising System
sub
etRegPrcChg
cpRegPrcChg
RMSDBConn
ToandFromRMS
ewRegPrcChgToRMS colRegPrcChgToRMS
crRegPrcChgToRMS
RMSSUB_RegPrcChg
11.0.1
Regular Price Changes-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:Transform Notes:
Filter Notes:Routing Notes:
General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
regprcchgmod RegPrcChgDesc RegPrcChgDesc
regprcchgcre RegPrcChgDesc RegPrcChgDesc
regprcchgdel RegPrcChgRef RegPrcChgRef
Thursday, October 28, 2004 Page 114 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
RTV rtv
RTV.jpg
Whenever merchandise is returned to the vendor, RDM publishes return-to-vendor (RTV) messages to the RIB. RMS subscribes to these messages in order to update inventory quantiand stock ledger values.
Return To VendorFamily Description:Functional Description:Family Diagram:
11.0
RWMS Retek Warehouse Distribution Management
PUB
etRTVFromRDMMFM
cpToAndFromRDMWH##
etRTV
cpRTV
ewRTVFromRDMWH## colRTVFromRDMWH##
crRTVFromRDM
facility_type
RDMMFM_RTV
O_STATUS_CODE VARCHAR2 OUT, O_ERROR_MSG VARCHAR2 OUT, O_MESSAGE_TYPE VARCHAR2 OUT, O_MESSAGE RIB_OBJECT OUT, O_BUS_OBJ_ID RIB_BUSOBJID_TBLOUT, O_ROUTING_INFO RIB_ROUTINGINFO_TBL OUT, I_NUM_THREADS NUMBER IN DEFAULT, I_THREAD_VAL NUMBER IN DEFAULT, I_FACILITY_TYPE VARCHAR2 IN, I_DC_DEST_ID VARCHAR2 IN
RTV_QUEUE
10.3
RTV-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:Transform Notes:
Filter Notes:Routing Notes:
General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
RIB_RTVDesc_RECCreateRTVRibObjects.sql
rtvcre RTVDesc RTVDesc
Thursday, October 28, 2004 Page 115 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
O_STATUS_CODE OUT VARCHAR2, O_ERROR_MSG OUT VARCHAR2, O_MESSAGE OUT RIB_OBJECT, O_MESSAGE_TYPE IN/OUT VARCHAR2, O_BUS_OBJ_ID IN/OUT NOCOPY RIB_BISOBJID_TBL, O_ROUTING_INFO IN/OUT NOCOPY RIB_ROUTINGINFO_TBL
RIB_MESSA
10.1.9, 10.2.2
Season-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:Transform Notes:
Filter Notes:Routing Notes:
General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
seasonmod SeasonDesc SeasonDesc
seasondtlmod SeasonDesc SeasonDesc
seasoncre SeasonDesc SeasonDesc
seasondel SeasonRef SeasonRef
seasondtldel SeasonRef SeasonRef
seasondtlcre SeasonDesc SeasonDesc
Thursday, October 28, 2004 Page 121 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
SeedData seeddata
Seed Data 10.3.jpg
The seed data message is a common publisher for differentiator types and codes from RMS.
Seed data will be published through this interface. Currently DiffTypes and Code Head/Detail are included.Family Description:Functional Description:Family Diagram:
11.0
RIB Retek Integration Bus
TAFR
etSeedData
Calls Subscriber Injector Directly
com.retek.rib.collab.tafr.See
This uses a default TAFR implementation that allows you to filter message types that the applciation does not want. The property is tafr.types.filter.[familyName] = [Valid Message types]
com.retek.component.codes
Payload
11.0
SeedData-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:
Filters out messages not listed in the properties file. Various Different parts of seed data are filtered out.
Transform Notes:Filter Notes:
Routing Notes:General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
CodeHdrMod CodeDtlDesc CodeDtlDesc
CodeHdrCre CodeHdrDesc CodeHdrDesc
CodeDtlMod CodeHdrDesc CodeHdrDesc
CodeDtlCre CodeDtlDesc CodeDtlDesc
DiffTypeMod DiffTypeDesc DiffTypeDesc
DiffTypeCre DiffTypeDesc DiffTypeDesc
Thursday, October 28, 2004 Page 122 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Thursday, October 28, 2004 Page 126 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
seedobj seedobj
This family is a common publisher for RMS foundation Data. The foundation data being published through this message includes Country and Currency Rates.
This family is a common publisher for RMS foundation Data.Family Description:Functional Description:Family Diagram:
11.0
RMS Retek Merchandising System
PUB
etSeedObjFromRMSMFM
cpToAndFromRMS
etSeedObjFromRMS
cpSeedObj
ewSeedObjFromRMS colSeedObjFromRMS
crSeedObjFromRMS
RMSMFM_SeedObj
11.0, 10.1.9, 10.2
seedobj-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:Transform Notes:
Filter Notes:Routing Notes:
General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
countrymod CountryDesc CountryDesc
currratemod CurrRateDesc CurrRateDesc
countrycre CountryDesc CountryDesc
countrydel CountryRef CountryRef
currratecre CurrRateDesc CurrRateDesc
Thursday, October 28, 2004 Page 127 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
SKUOptm skuoptm
SKU Opt 10.3.jpg
The RDM application does not currently support warehouse optimization functionality related to SKU profiling. To close this functional gap, Retek has partnered with Streamsoft to integwith the FlowTrak application. The objective of FlowTrak is to continually maintain an optimal SKU profile by accounting for factors that influence the movement, staging, and storage oSKUs and their cost impact to the operation.
This uses a default TAFR implementation that allows you to filter message types that the applciation does not want. The property is tafr.types.filter.[familyName] = [Valid Message types]
colSOStatusToSOStatusCOFromRIB
None
com.retek.component.custo
Payload
11.0
SOStatus-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:
This eway only allows Stock Order status messages that are related to Customer Orders. Additional SO Status messages could be related to allocations and transfers. If consumer direct flag is NOT set to Y then it is dropped.
O_STATUS_CODE VARCHAR2 IN/OUT, O_ERROR_MESSAGE VARCHAR2 IN/OUT, I_MESSAGE RIB_OBJECT IN, I_MESSAGE_TYPE VARCHAR2 IN
11.0, 10.1.9, 10.2
SOStatus-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:
This eway only allows Stock Order status messages that are related to allocations and transfers. Additional SO Status messages coulbe related to Customer Orders. If consumer direct flag is set to Y then it is dropped.
Thursday, October 28, 2004 Page 132 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
SIM Store Inventory Management
PUB
etSOStatus
cpSOStatus
sostatuspublisher.cfg
stkcountpublisher.cfg
10.4
SOStatus-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:Transform Notes:
Filter Notes:Routing Notes:
General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
sostatuscre SOStatusDesc SOStatusDesc
sostatuscre SOStatusDesc SOStatusDesc
Thursday, October 28, 2004 Page 133 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
RCOM Retek Customer Order Management
SUB
etSOStatus
cpSOStatus
SOStatusToRCOM
com.retek.component.custo
Payload
11.0
SOStatus-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:Transform Notes:
Filter Notes:Routing Notes:
General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
sostatuscre SOStatusDesc SOStatusDesc
Thursday, October 28, 2004 Page 134 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
SpaceLocs spacelocs
Locations are published to the RIB via the Publish Location Data menu object within RDM. All locations within RDM are sent via a batch file to the third party application for import into system. The third party system determines how the locations will be inserted based on import logic built into its system. The RIB is responsible for the transfer of the batch file from RDthe third party system.
Space LocationsFamily Description:Functional Description:Family Diagram:
11.0
RWMS Retek Warehouse Distribution Management
PUB
etSpaceLocsFromRDMMFM
cpToAndFromRDMWH##
etSpaceLocs
cpSpaceLocs
ewSpaceLocsFromRDMWH colSpaceLocsFromRDMWH##
crSpaceLocsFromRDMWH1
RDMMFM_SpaceLocs
O_STATUS_CODE VARCHAR2 OUT, O_ERROR_MSG VARCHAR2 OUT, O_MESSAGE_TYPE VARCHAR2 OUT, O_MESSAGE RIB_OBJECT OUT, O_BUS_OBJ_ID RIB_BUSOBJID_TBLOUT, O_ROUTING_INFO RIB_ROUTINGINFO_TBL OUT, I_NUM_THREADS NUMBER IN DEFAULT, I_THREAD_VAL NUMBER IN DEFAULT, I_FACILITY_TYPE VARCHAR2 IN, I_DC_DEST_ID VARCHAR2 IN
Thursday, October 28, 2004 Page 137 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
Stock Order stockorder
Stock Orders 10.3.jpg
RMS publishes transfer and allocation messages; RCOM publishes customer order messages. Both of these are transformed by TAFRs to stock order messages, which are subscribedby RDM.
O_STATUS_CODE VARCHAR2 OUT, O_ERROR_MESSAGE VARCHAR2 OUT, I_MESSAGE RIB_OBJECT IN, I_MESSAGE_TYPE VARCHAR2 IN, I_FACILITY_TYPE VARCHAR2 IN
10.3
Stock Order-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:Transform from to Allocation to Stock Order. The content of the message will be exactly the same.
This eway will ERROR out and shut down if the location ID on the Transfer or Allocation is not setup in RIB.Properties. If it is setup, it add an additional location instance to the end of the Topic name. i.e. WH1
Transform Notes:Filter Notes:
Routing Notes:
General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
sodesc.dtdsodtlmod SODesc SODesc
sodesc.dtdsodtlcre SODesc SODesc
soref.dtdsohdrdel SORef SORef
soref.dtdsodtldel SORef SORef
Thursday, October 28, 2004 Page 138 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Routing Information:Transform from Customer Order to Stock Order
This eway will ERROR out and shut down if the location ID on the Customer Order is not setup in RIB.Properties. If it is setup, it will aan additional location instance to the end of the Topic name. i.e. WH1
Transform Notes:Filter Notes:
Routing Notes:
General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
SODesc.dtdsocre SODesc SODesc
SODtlRef.dtdsodtldel SORef SORef
SOHdrDesc.dtdsohdrmod SODesc SODesc
SOHdrRef.dtdsohdrdel SORef SORef
SODtlDesc.dtdsodtlcre SODesc SODesc
SODtlDesc.dtdsodtlmod SODesc SODesc
Thursday, October 28, 2004 Page 139 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
RWMS Retek Warehouse Distribution Management
SUB
etStockOrdersFromRIBToWH#
cpStockOrders
etRDMDBConn
cpToAndFromRDMWH##
ewStockOrderToRDMWH# colStockOrderToRDMWH#
cpStockOrderToRDM
colStockOrderToRDMWH#
RDMSUB_SO
O_STATUS_CODE VARCHAR2 OUT, O_ERROR_MESSAGE VARCHAR2 OUT, I_MESSAGE RIB_OBJECT IN, I_MESSAGE_TYPE VARCHAR2 IN, I_FACILITY_TYPE VARCHAR2 IN
O_STATUS_CODE VARCHAR2 OUT, O_ERROR_MESSAGE VARCHAR2 OUT, I_MESSAGE RIB_OBJECT IN, I_MESSAGE_TYPE VARCHAR2 IN, I_FACILITY_TYPE VARCHAR2 IN
10.3
Stock Order-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:Transform from Transfer to Stock Order
This eway will ERROR out and shut down if the location ID on the Transfer or Allocation is not setup in RIB.Properties. If it is setup, it add an additional location instance to the end of the Topic name. i.e. WH1
Transform Notes:Filter Notes:
Routing Notes:
General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
sodtldel SORef SORef
sodtlcre SODesc SODesc
sohdrdel SORef SORef
socre SODesc SODesc
sohdrmod SODesc SODesc
sodtlmod SODesc SODesc
Thursday, October 28, 2004 Page 141 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Thursday, October 28, 2004 Page 142 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
Stores stores
Stores.jpg
For Retek 10 Integration Bus purposes, the word "locations" can apply to: Stores and warehouses in RMS; Virtual stores and warehouses in RCOM�* Ship methods in RCOM�* Physlocations in RDM�RMS publishes stores and warehouses (both physical and virtual) to the RIB using the e*Ways:�* ewStoresFromRMS�* ewWHFromRMS �RCOM publishes ship methods to the RIB using the e*Way:�* ewShipMethFromRCOM�RCOM subscribes to virtual stores and warehouses, and RDM subscribes to locations. In a multi-channel environmenbefore a location can be successfully consumed by the subscribing application, any channels or banners that the location references must have already been successfully consumed bysame subscribing application.
StoresFamily Description:Functional Description:
Family Diagram:
11.0.1
RIB Retek Integration Bus
TAFR
etStore
Calls Subscriber Injector Directly
com.retek.rib.collab.tafr.Def
This uses a default TAFR implementation that allows you to filter message types that the applciation does not want. The property is tafr.types.filter.[familyName] = [Valid Message types]
com.retek.component.locati
Payload
11.0
Stores-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:
Filters out messages not listed in the properties file. No deletes are excepted.
Transform Notes:Filter Notes:
Routing Notes:General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
storecre StoreDesc StoreDesc
storemod StoreDesc StoreDesc
Thursday, October 28, 2004 Page 143 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
RMS Retek Merchandising System
PUB
etStoresFromRMSMFM
cpToAndFromRMS
etStoresFromRMS
cpStores
ewStoresFromRMS colStoresFromRMS
crStoresFromRMS
location_type
RMSMFM_Store
O_STATUS_CODE OUT VARCHAR2, O_ERROR_MSG OUT VARCHAR2, O_MESSAGE OUT RIB_OBJECT, O_MESSAGE_TYPE IN/OUT VARCHAR2, O_BUS_OBJ_ID IN/OUT NOCOPY RIB_BUSOBJID_TBL, O_ROUTING_INFO IN/OUT NOCOPY RIB_ROUTINGINFO_TBL
RIB_MESSASTORE_MFQUEUE
11.0, 10.1.9, 10.2
Stores-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:Transform Notes:
Filter Notes:Routing Notes:
General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
StoreRef.dtdstoredel StoreRef StoreRef
StoreDesc.dtdstoremod StoreDesc StoreDesc
StoreDesc.dtdstorecre StoreDesc StoreDesc
Thursday, October 28, 2004 Page 144 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
This eway will create one message that is etLocationFromRIB (These messages only contain physical Warehouses) and one etStoresFromRIB (These messages only contain vitual messages)
colStoresToLocationFromRIB
Store ID, Location ID
Stores-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:This eway transforms Stores to a location message. No contents of the message are actually changed. Format only.Transform Notes:
Filter Notes:Routing Notes:
General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
StoreDesc.dtdstoremod StoreDesc StoreDesc
StoreRef.dtdstoredel StoreRef StoreRef
StoreDesc.dtdstorecre StoreDesc StoreDesc
Thursday, October 28, 2004 Page 145 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Thursday, October 28, 2004 Page 147 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
RCOM Retek Customer Order Management
SUB
etStores
cpStores
StoresToRCOM
com.retek.component.locati
Payload
11.0
Stores-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:Transform Notes:
Filter Notes:Routing Notes:
General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
storecre StoreDesc StoreDesc
storemod StoreDesc StoreDesc
Thursday, October 28, 2004 Page 148 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
Transfers transfers
Transfers.jpg
RMS publishes transfer and allocation messages; RCOM publishes customer order messages. Both of these are transformed by TAFRs to stock order messages, which are subscribedby RDM.
Thursday, October 28, 2004 Page 150 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
UDAs udas
UDAs.jpg
RMS 10.2 publishes messages about user-defined attributes (UDAs) to the RIB. UDAs provide a method for defining attributes and associating the attributes with specific items. UDA's useful for information and reporting purposes. UDA's can be defined in one of three formats: Date, Freeform text or List of Values (LOV). However, for Retek 10.2 Integration, the RIB fall formats except LOV by the UDA to UDA LV TAFR.
This uses a default TAFR implementation that allows you to filter message types that the applciation does not want. The property is tafr.types.filter.[familyName] = [Valid Message types]
com.retek.component.item.i
Payload
11.0
UDAs-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:
Filters out messages not listed in the properties file.
Transform Notes:Filter Notes:
Routing Notes:General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
udavalmod UDAValDesc UDAValDesc
udavalcre UDAValDesc UDAValDesc
udahdrcre UDADesc UDADesc
udahdrmod UDADesc UDADesc
Thursday, October 28, 2004 Page 151 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
This uses a default TAFR implementation that allows you to filter message types that the applciation does not want. The property is tafr.types.filter.[familyName] = [Valid Message types]
com.retek.component.suppli
Payload
11.0
Vendor-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:
Filters out messages not listed in the properties file. No deletes are excepted.
Transform Notes:Filter Notes:
Routing Notes:General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
vendorhdrmod VendorHdrDesc VendorHdrDesc
vendorcre VendorDesc VendorDesc
vendoraddrmod VendorAddrDesc VendorAddrDesc
vendoraddrcre VendorAddrDesc VendorAddrDesc
Thursday, October 28, 2004 Page 156 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Thursday, October 28, 2004 Page 161 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
Warehouses wh
WH.jpg
For Retek 10 Integration Bus purposes, the word "locations" can apply to: Stores and warehouses in RMS; Virtual stores and warehouses in RCOM�* Ship methods in RCOM�* Physilocations in RDM�RMS publishes stores and warehouses (both physical and virtual) to the RIB using the e*Ways:�* ewStoresFromRMS�* ewWHFromRMS �RCOM publishes ship methods to the RIB using the e*Way:�* ewShipMethFromRCOM�RCOM subscribes to virtual stores and warehouses, and RDM subscribes to locations. In a multi-channel environmenbefore a location can be successfully consumed by the subscribing application, any channels or banners that the location references must have already been successfully consumed bysame subscribing application.
This uses a default TAFR implementation that allows you to filter message types that the applciation does not want. The property is tafr.types.filter.[familyName] = [Valid Message types]
com.retek.component.locati
Payload
11.0
Warehouses-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:
Filters out messages not listed in the properties file. No deletes are excepted.
Transform Notes:Filter Notes:
Routing Notes:General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
whmod WHDesc WHDesc
whcre WHDesc WHDesc
Thursday, October 28, 2004 Page 162 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
RMS Retek Merchandising System
PUB
etWHFromRMSMFM
cpToAndFromRMS
etWHFromRMS
cpWH
ewWHFromRMS colWHFromRMS
crWHFromRMS
location_type
RMSMFM_WH
O_STATUS_CODE OUT VARCHAR2, O_ERROR_MSG OUT VARCHAR2, O_MESSAGE OUT RIB_OBJECT, O_MESSAGE_TYPE IN/OUT VARCHAR2, O_BUS_OBJ_ID IN/OUT NOCOPY RIB_BUSOBJID_TBL, O_ROUTING_INFO IN/OUT NOCOPY RIB_ROUTINGINFO_TBL
RIB_MESSAWH_MFQUEUE
11.0, 10.1.9, 10.2
Warehouses-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:Transform Notes:
Filter Notes:Routing Notes:
General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
WHRef.dtdwhdel WHRef WHRef
WHDesc.dtdwhmod WHDesc WHDesc
WHDesc.dtdwhcre WHDesc WHDesc
Thursday, October 28, 2004 Page 163 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
RIB Retek Integration Bus
TAFR
etWHFromRMS
cpWH
etLocationsFromRIB:etWHFromRIB
cpLocations:cpWH
ewWHToLocationsFrom RIB colWHToLocationsFrom RIB
crWHToLocationsFrom RIB
Location_type
This eway will create one message that is etLocationFromRIB (These messages only contain physical Warehouses) and one etStoresFromRIB (These messages only contain vitual messages)
colWHToLocationsFrom RIB
Warehouse ID, Location ID
Warehouses-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:This eway transforms messages from a warehouse format to a location formatted messageTransform Notes:
Filter Notes:Routing Notes:
General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
WHDesc.dtdwhcre WHDesc WHDesc
WHRef.dtdwhdel WHRef WHRef
WHDesc.dtdwhmod WHDesc WHDesc
Thursday, October 28, 2004 Page 164 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
RIB Retek Integration Bus
TAFR
etWHFromRMS
cpWH
etWHToWHPhysFromRIB
cpWH
ewWHToWHPhysFromRIB colWHToWHPhysFromRIB
crWHToWHPhysFromRIB
Location_type
colWHToWHPhysFromRIB
WH ID
Warehouses-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:
This eway subscribes to all WH messages and only republishes the physical warehouses. All virtual warehouses are dropped.
Transform Notes:Filter Notes:
Routing Notes:General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
WHDesc.dtdwhcre WHDesc WHDesc
WHRef.dtdwhdel WHRef WHRef
WHDesc.dtdwhmod WHDesc WHDesc
Thursday, October 28, 2004 Page 165 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Thursday, October 28, 2004 Page 177 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
RIB Retek Integration Bus
TAFR
etWOInFromRMS
cpWOIn
etWOInFromRIBToWH##
cpWOIn
ewWOInToWOInWHFromRI colWOInToWOInWHFromRIB
crWOInToWOInWHFromRIB
facility_id
colWOInToWOInWHFromRIB
Work Order ID, Work Order ID and Locatio
Work Order (Inbound)-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:
This eway will ERROR out and shut down if the location ID on the Work Order is not setup in RIB.Properties. If it is setup, it will add aadditional location instance to the end of the Topic name. i.e. WH1
Transform Notes:Filter Notes:
Routing Notes:
General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
WOInDesc.dtdinbdwomod WOInDesc WOInDesc
WOInDesc.dtdinbdwodel WOInRef WOInRef
WOInRef.dtdinbdwocre WOInDesc WOInDesc
Thursday, October 28, 2004 Page 178 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
Work Order (Outbound) woout
WO Out.jpg
A work order provides direction to RDM about work that needs to be completed on items contained in a recent stock order. A publisher would publish a new work order messages soonafter it publishes the stock order message. RDM subscribes to work order messages in order to determine the tasks that need to be completed at the warehouse.
Work Order OutboundFamily Description:Functional Description:Family Diagram:
11.0
RMS Retek Merchandising System
PUB
etRMSDBConn
cpToAndFromRMS
etWOOut
cpWOOut
ewWOOutFromRMS colWOOutFromRMS
crWOOutFromRMS
colWOOutFromRMS
RMSMFM_WOOUT
11.0
Work Order (Outbound)-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:Transform Notes:
Filter Notes:Routing Notes:
General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
RIB_WOOUTDESC_RECCreateWOOutRibObjects.sql
outbdwocre WOOutDesc WOOutDesc
RIB_WOOUTREF_RECCreateWOOutRibObjects.sql
outbdwodel WOOutRef WOOutRef
RIB_WOOUTDESC_RECCreateWOOutRibObjects.sql
outbdwomod WOOutDesc WOOutDesc
Thursday, October 28, 2004 Page 179 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
RWMS Retek Warehouse Distribution Management
SUB
etWOOut
cpWOOut
etRDMDBConn
cpToAndFromRDMWH##
ewWOOutToRDMWH## colWOOutToRDMWH##
crWOOutToRDM
colWOOutToRDMWH##
RDMSUB_WOOut
O_STATUS_CODE VARCHAR2 OUT, O_ERROR_MSG VARCHAR2 OUT, O_MESSAGE_TYPE VARCHAR2 OUT, O_MESSAGE RIB_OBJECT OUT, O_BUS_OBJ_ID RIB_BUSOBJID_TBLOUT, O_ROUTING_INFO RIB_ROUTINGINFO_TBL OUT, I_NUM_THREADS NUMBER IN DEFAULT, I_THREAD_VAL NUMBER IN DEFAULT, I_FACILITY_TYPE VARCHAR2 IN, I_DC_DEST_ID VARCHAR2 IN
O_STATUS_CODE IN/OUT VARCHAR2, O_ERROR_MESSAGE IN/OUT VARCHAR2, I_MESSAGE IN RIB_OBJECT, I_MESSAGE_TYPE IN VARCHAR2
11.0
XCostChg-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:Transform Notes:
Filter Notes:Routing Notes:
General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
RIB_XCOSTCHGDESC_RECCreateXCostChgRibObjects.sql
xcostchgmod XCostChgDesc XCostChgDesc
Thursday, October 28, 2004 Page 187 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
XDiffGrp xdiffgrp
XDiff Grp.jpg
The external differentiator group message is used to send diff group data to the RMS system from external or legacy systems. Diff groups are logical groupings of differentiators such apants sizes, shirt colors or flavors.
Thursday, October 28, 2004 Page 188 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
RIB_XDIFFGRPDESC_RECCreateXDiffGrpRibObjects.sql
xdiffgrpmod XDiffGrpDesc XDiffGrpDesc
RIB_XDIFFGRPREF_RECCreateXDiffGrpRibObjects.sql
xdiffgrpdel XDiffGrpRef XDiffGrpRef
RIB_XDIFFGRPDESC_RECCreateXDiffGrpRibObjects.sql
xdiffgrpcre XDiffGrpDesc XDiffGrpDesc
RIB_XDIFFGRPDESC_RECCreateXDiffGrpRibObjects.sql
xdiffgrpdtlcre XDiffGrpDesc XDiffGrpDesc
RIB_XDIFFGRPDESC_RECCreateXDiffGrpRibObjects.sql
xdiffgrpdtlmod XDiffGrpDesc XDiffGrpDesc
RIB_XDIFFGRPREF_RECCreateXDiffGrpRibObjects.sql
xdiffgrpdtldel XDiffGrpRef XDiffGrpRef
Thursday, October 28, 2004 Page 189 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
XDiffID xdiffid
XDiff ID.jgp
The external differentiator id message is used to send differentiator data to the RMS system from external or legacy systems. The differentiators are further distinguishing characteristicitems.
O_STATUS_CODE IN/OUT VARCHAR2,O_ERROR_MESSAGE IN/OUT VARCHAR2,I_MESSAGE IN RIB_OBJECT,I_MESSAGE_TYPE IN VARCHAR2
11.0
XItem-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:Transform Notes:
Filter Notes:Routing Notes:
General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
RIB_XITEMDESC_RECCreateXItemRibObjects.sql
xitemcre XItemDesc XItemDesc
RIB_XITEMREF_RECCreateXItemRibObjects.sql
xitemdel XItemRef XItemRef
RIB_XITEMDESC_RECCreateXItemRibObjects.sql
xitemmod XItemDesc XItemDesc
Thursday, October 28, 2004 Page 191 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
RIB_XITEMDESC_RECCreateXItemRibObjects.sql
xitemsupcre XItemDesc XItemDesc
RIB_XITEMDESC_RECCreateXItemRibObjects.sql
xitemsupctycre XItemDesc XItemDesc
RIB_XITEMREF_RECCreateXItemRibObjects.sql
xitemsupctydel XItemRef XItemRef
RIB_XITEMDESC_RECCreateXItemRibObjects.sql
xitemsupctymod XItemDesc XItemDesc
RIB_XITEMREF_RECCreateXItemRibObjects.sql
xitemsupdel XItemRef XItemRef
RIB_XITEMDESC_RECCreateXItemRibObjects.sql
xitemsupmod XItemDesc XItemDesc
RIB_XITEMDESC_RECCreateXItemRibObjects.sql
xitemvatcre XItemDesc XItemDesc
RIB_XITEMREF_RECCreateXItemRibObjects.sql
xitemvatdel XItemRef XItemRef
RIB_XITEMDESC_RECCreateXItemRibObjects.sql
xizpcre XItemDesc XItemDesc
RIB_XITEMDESC_RECCreateXItemRibObjects.sql
xiscloccre XItemDesc XItemDesc
RIB_XITEMREF_RECCreateXItemRibObjects.sql
xisclocdel XItemRef XItemRef
RIB_XITEMDESC_RECCreateXItemRibObjects.sql
xisclocmod XItemDesc XItemDesc
Thursday, October 28, 2004 Page 192 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
RCOM Retek Customer Order Management
SUB
etItems
cpItems
ItemsToRCOM
com.retek.component.item.i
Payload
11.0
XItem-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:Transform Notes:
Filter Notes:Routing Notes:
General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
xitemcre XItemDesc XItemDesc
xitemsupmod XItemDesc XItemDesc
xitemsupcre XItemDesc XItemDesc
xitemmod XItemDesc XItemDesc
xitemsupctymod XItemDesc XItemDesc
xitemsupctycre XItemDesc XItemDesc
Thursday, October 28, 2004 Page 193 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
XItemLoc xitemloc
XItemLoc.jpg
The external item location message is used to send item location data to the RMS system from external or legacy systems. Item locations are used to provide information about specifiitems and physical or virtual locations where inventory may exist.
O_STATUS_CODE IN/OUT VARCHAR2,O_ERROR_MESSAGE IN/OUT VARCHAR2,I_MESSAGE IN RIB_OBJECT,I_MESSAGE_TYPE IN VARCHAR2
11.0
XItemLoc-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:Transform Notes:
Filter Notes:Routing Notes:
General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
RIB_XITEMLOCDESC_RECCreateXItemLocRibObjects.sql
xitemlocmod XItemLocDesc XItemLocDesc
RIB_XITEMLOCDESC_RECCreateXItemLocRibObjects.sql
xitemloccre XItemLocDesc XItemLocDesc
Thursday, October 28, 2004 Page 194 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
XItemRcls xitemrcls
XItem Rcls.jpg
The external item reclassification message is used to send item reclassification information to the RMS system from external or legacy systems. Item reclass data is used to move itemfrom one place in the item hierarchy to another place, example, from one subclass to another.
Thursday, October 28, 2004 Page 195 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
RIB_XITEMRCLSREF_RECCreateXItemRclsRibObjects.sql
xitemrclsdtldel XItemRclsRef XItemRclsRef
Thursday, October 28, 2004 Page 196 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
XLocTrt xloctrt
XLocTrt.jpg
The external location traits message is used to send location traits data to the RMS system from external or legacy systems. Location traits are means of grouping locations by commocharacteristics.
Thursday, October 28, 2004 Page 199 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
Thursday, October 28, 2004 Page 200 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
XMrchHrRcls xmrchhrrcls
XMrchHrRcls.jpg
The external merchandising hierarchy reclass message is used to send merchandise hierarchy reclassification data to the RMS system from external or legacy systems. Merchandise hierarchy reclass data provides information about items that have been reclassified, or moved, from one hierarchical level to another.
O_STATUS_CODE IN/OUT VARCHAR2,O_ERROR_MESSAGE IN/OUT VARCHAR2,I_MESSAGE IN RIB_OBJECT,I_MESSAGE_TYPE IN VARCHAR2
11.0, 10.1.9, 10.2
XOrder-
Application:
Process Name: Collaboration:Collaboration Rule:
Subscriber Topic:Subscriber Connection:
Publisher Topic:Publisher Connection:
Durable Subscriber:Business Object ID:
Routing Information:Transform Notes:
Filter Notes:Routing Notes:
General Comments:
Message Type
Object Name
Retek Binding Mapping/Oracle Object Script
Data Definition Name RIB Doc Type Name
API Name:
Parameters:
Pub Hospital:Stagging Tables:
Version:
XOrderMod XOrderDesc XOrderDesc
XOrderDtlMod XOrderDesc XOrderDesc
XOrderCre XOrderDesc XOrderDesc
XOrderDel XOrderRef XOrderRef
XOrderDtlDel XOrderRef XOrderRef
XOrderDtlCre XOrderDesc XOrderDesc
Thursday, October 28, 2004 Page 202 of 209Retek® Integration Bus™ is a trademark of Retek Inc.
Integration Guide Release: 11.0.1
XOrgHr xorghr
XOrgHr.jpg
The external organizational hierarchy message is used to send organizational hierarchy data to the RMS system from external or legacy systems. The organizational hierarchy messagrefers to the relationships between company, chain, area, region, district, store, etc. of the company.