13 Procure to Pay

This section describes the common functionality and configurations available for Procure to Pay.

Procure to Pay features include the possibility of creating and maintaining Purchase Orders, Shipments and create Finance Documents. It also includes the functionality of downloading and uploading majority of those entries being a more effective way to maintain in bulk. Each of the entities maintained in Procure to Pay have specific sections to details of the implementation details.

Purchase Orders

This section describes the Purchase Orders features.

Implementation Overview

This section provides an implementation overview of the Purchase Orders functionality.

Functionality

Procure to Pay, Purchase Orders, will allow retailers and suppliers to create and maintain purchase orders.

Status Workflow

Figure 13-1 Procure to Pay Purchase Orders Status Workflow


Procure to Pay Purchase Orders Status Workflow

Purchase Order follows a workflow path, and the status can change depending on:

  • The user permissions
  • The current status of the purchase order

Purchase Order Status:

  • New – New is the initial status of a Purchase Order. In this status a Purchase Order can be approved to send the Purchase Order to MFCS or Rejected to change the status of the Purchase Order to rejected.
  • Rejected – Reject status is for Purchase Orders that were not previously approved.
  • Approved – This status is used after the Purchase Order is Approved, in this state the Order has been sent to MFCS.
  • Changes Proposed – Changes proposed is the status used when a user without approval permissions updates an approved Purchase Order. During this status the changes made on the purchase order can be approved and then sent to MFCS or rejected and the changes are discarded.
  • Cancelled – Cancelled status is used when the Purchase Order is cancelled in Procure to Pay.
  • Shipped – Shipped status is used whenever a shipment has been created for the Purchase Order.
  • Closed – Closed is the final status of the order once MFCS closes the order. This status can also be used for MFCS side cancelled orders, i.e., not done via SCH.
Integration High Level

Figure 13-2 SPPP Purchase Order Integration Overview


SPPP Purchase Order Integration Overview

The integration of Purchase Orders from Procure to Pay to MFCS described above is done in the following order:

  • Purchase Orders are created and managed in Procure to Pay, either through the UI or via upload functionality.
  • After being approved or cancelled, Purchase Orders are published by a batch process.
  • Purchase Orders Induction Java Services adds Purchase Orders to an MFCS induction file, which is transferred to MFCS SFTP/FTS.
  • Finally, MFCS induction batch for Purchase Orders is executed and integrates Purchase Orders to MFCS.

Configuration

This section describes the Procure to Pay configuration.

POM Configuration

Batch scheduler details with all batches, dependencies and frequencies can be downloaded following the steps in the Supply Chain Hub Frameworks section.

Schedule Overview

Figure 13-3 Procure to Pay Purchase Orders Batch Schedule Overview


Procure to Pay Purchase Orders Batch Schedule Overview

Other Cloud Services Configuration

This section describes implementation details that must be reviewed from an Oracle Retail Merchandising System perspective.

Batches

The MFCS integration order induction job, POINDUCT_JOB, should be configured to execute with high frequency to assure that purchase orders changes made in Procure to Pay are integrated into MFCS as soon as possible with final target the merchandising tables via parameter “RMS”.

Other Implementation Considerations

This section describes implementation considerations for Purchase Order features.

Custom Validations - Purchase Orders

The module performs validations by implementing Custom Validation Groups of the Custom Validations Framework described in the Supply Chain Hub Frameworks section. The groups listed below can be used to add Custom Validations for Purchase Orders.

Group Id Executed When
SPPP_ORDER_APPROVE Purchase Order is Approved
SPPP_ORDER_CANCEL Purchase Order is Cancelled
SPPP_ORDER_REJECT Purchase Order is Rejected
SPPP_ORDER_SUBMIT Purchase Order is Submitted for Approval
Materialized Views

This application requires some results to be materialized in tables using the Materialized View Framework described in the Supply Chain Hub Frameworks section, below is the list for this application. Materialized views used in Procure to Pay, Purchase Orders, are listed in this section.

ORCV_MV_SPPP_DASH_ALL_PO

Materialize View to support Supply Chain Hub dashboard “All POs Available” showing all Purchase Orders available.

  • Pre-Dependencies: None
  • Post-Dependencies: None
  • Frequency: Ad-hoc.
ORCV_MV_SPPP_DASH_PO_NEW
Materialize View to support Supply Chain Hub dashboard “New POs to be Approved” showing Purchase Orders with Status "New".
  • Pre-Dependencies: None
  • Post-Dependencies: None
  • Frequency: Ad-hoc
ORCV_MV_SPPP_DASH_PO_PENDING

Description: Materialize View to support Supply Chain Hub dashboard “POs Pending Action” showing Purchase Orders with pending actions by Status.

Pre-Dependencies: None

Post-Dependencies: None

Frequency: Ad-hoc.

ORCV_MV_SPPP_DASH_PO_QTY_L5W

Materialize View to support Supply Chain Hub dashboard “PO Quantity Expected” showing Purchase Orders expected Quantities.

  • Pre-Dependencies: None
  • Post-Dependencies: None
  • Frequency: Ad-hoc.
ORCV_MV_SPPP_DASH_PO_WAIT_ASN

Materialize View to support Supply Chain Hub dashboard “POs Waiting Shipment” showing Purchase Orders with Status "Approved" without shipment.

  • Pre-Dependencies: None
  • Post-Dependencies: None
  • Frequency: Ad-hoc.
ORCV_MV_SPPP_DASH_PO_WAIT_DOC

Materialize View to support Supply Chain Hub dashboard “POs Waiting Invoices” showing Purchase Orders with Status "Approved" or "Closed" without invoice.

  • Pre-Dependencies: None
  • Post-Dependencies: None
  • Frequency: Ad-hoc.
ORCV_MV_SPPP_DASH_PO_WAIT_REV

Materialize View to support Supply Chain Hub dashboard “POs Waiting Review” showing Purchase Orders with Status "Changes Proposed" without revision.

  • Pre-Dependencies: None
  • Post-Dependencies: None
  • Frequency: Ad-hoc.
ORCV_MV_SPPP_PO_LAST_REV

Revision number for Purchase Orders.

Pre-Dependencies: None

Post-Dependencies: None

Frequency: Ad-hoc, Nightly

ORCV_MV_SPPP_PO_REJ_CANCEL

Returns the number of cancelled and rejected POs, by supplier and department displayed in Procure to Pay Home page.

Pre-Dependencies: None

Post-Dependencies: None

Frequency: Ad-hoc.

ORCV_MV_SPPP_PO_TOTALS

Returns the total quantity and total cost of the POs, displayed in Procure to Pay Home page grid.

  • Pre-Dependencies: None
  • Post-Dependencies: None
  • Frequency: Ad-hoc.
Codes

Certain operations require codes to define the options available at system level. Below you can find the list of code types available.

The codes are defined in the ORCV_CODE_HEAD and ORCV_CODE_DETAIL tables.

Table 13-1 Codes

CODE TYPE CODE TYPE DESCRIPTION
ORRC Purchase Order Reason Codes
ORST Purchase Order Status
ORTP Purchase Order Type
PRTP Purchase Order Type
PYMT Payment Method
Templates

Procure to Pay, Purchase Orders, uses a spreadsheet download and upload process, developed as part of the Supply Chain Hub Frameworks framework, for creation, maintenance, and extraction of data. To support these processes there are some templates which must be configured, and several configurations should be reviewed as part of the implementation.

Templates SPPP Purchase Orders Data

Table 13-2 Template Key: SPPP_PURCHASE_ORDER_DATA

ACTION TYPE ROLE NAME
Download ORCV_SPPP_ORDER_APPR_JOB
Download ORCV_SPPP_ORDER_EDIT_JOB
Download ORCV_SPPP_ORDER_VIEW_JOB
Download Blank ORCV_SPPP_APP_JOB
Upload ORCV_SPPP_ORDER_APPR_JOB
Upload ORCV_SPPP_ORDER_EDIT_JOB

Table 13-3 Orders Worksheet

ACTION STATUS MANDATORY CELLS / FIELDS NOTES
Create New

Action,

Master order number, order number,

status,

location type, location,

supplier,

currency code, exchange rate

terms

When user has edit permissions

Create an order status New.

Create Approve

Action,

Master order number, order number,

status,

location type, location,

supplier,

currency code, exchange rate

terms

When user has approval permissions

Create an approved order

Update New

Action,

Master order number, order number,

status,

location type, location,

supplier,

currency code, exchange rate

terms

If the upload is done by a user with edit permissions, the order keeps the status New, if it is done by a user with approval permissions, the order status will change to Approved.

Update order/items data

(Applicable to scenarios where the order only exists in the SPPP application

Update

Approve

Action,

Master order number, order number,

status,

location type, location,

supplier,

currency code, exchange rate

terms

If the upload is done by a user with approval permissions, the order keeps the approved status, if it is done by a user with edit permissions, the order status will change to Change Proposed.

If the order does not yet exist in SPPP, the order will be created based on information that exists in MFCS

Update Change Proposed

Action,

Master order number, order number,

status,

location type, location,

supplier,

currency code, exchange rate

terms

If the upload is done by a user with edit permissions, the order keeps the change proposed status, if it is done by a user with approval permissions, the order status will change to Approved.

If the order does not yet exist in SPPP, the order will be created based on information that exists in MFCS.

Approve Not Applicable

Action,

Master order number, order number,

status,

location type, location,

supplier,

currency code, exchange rate

terms

When the user has approval permissions.

Only for order status evolution. The order will be approved (applicable to existing SPPP orders with status New or Change Proposed)

Order items worksheet data will not be used; worksheet can be left blank, or if there is data, leave the action field empty.

Acknowledge Not Applicable

Action,

Master order number, order number,

status,

location type, location,

supplier,

currency code, exchange rate

terms

When user has edit permissions.

This action will only be executed successfully if there is a higher approved order revision in the MFCS than the one in the SPPP.

If the order does not yet exist in SPPP, the order will be created based on information that exists in MFCS.

Order items worksheet data will not be used; worksheet can be left blank, or if there is data, leave the action field empty

Cancel Not Applicable

Action,

Master order number, order number,

status,

location type, location,

supplier,

currency code, exchange rate

terms

When the user has approval permissions.

Only for order status evolution. The order will be cancelled (applicable to existing orders with status Approve or Change Proposed).

If the order does not yet exist in SPPP, the order will be created based on information that exists in MFCS.

Order items worksheet data will not be used; worksheet can be left blank, or if there is data, leave the action field empty.

Reject Not Applicable

Action,

Master order number, order number,

status,

location type, location,

supplier,

currency code, exchange rate

terms

When the user has edit permissions, can only reject orders with status New.

When user has approval permissions, can reject order with status New and Change Proposed.

If the order has change proposed status, status orders will stay approve and order's data will be reverted to the last approved values.

Order items worksheet data will not be used; worksheet can be left blank, or if there is data, leave the action field empty.

Table 13-4 Order Items Worksheet

ACTION MANDATORY CELLS / FIELDS NOTES
Create

Action,

Quantity

Item or Reference Item or VPN

Supplier pack size

Country of sourcing

Add items to delivery.

Applicable when the action on the orders worksheet is Create or Update

Update

Action,

Quantity

Item or Reference Item or VPN

Supplier pack size

Country of sourcing

Update delivery items data

Applicable when the action on the orders worksheet is Update

Cancel

Action,

Item or Reference Item or VPN

Cancel delivery items data (zero out quantity value)

Applicable when the action on the orders worksheet is Update

Codes

Certain operations require codes to define the options available at system level. Below you can find the list of code types available.

The codes are defined in the ORCV_CODE_HEAD and ORCV_CODE_DETAIL tables.

CODE TYPE CODE TYPE DESCRIPTION
PPAC Purchase Order Actions
PPST Purchase Orders Status
PPIA Purchase Order Items Actions
Interactive Grid Additional Columns

This application supports adding additional fields to the Interactive Grids by using the Interactive Grid Additional Columns functionality described in the Supply Chain Hub Frameworks section.

The Interactive Grids that support this functionality are listed below:

Interactive Grid Grid ID User Types Page Non Based View Entity Key
Purchase Orders Dashboard Grid P1_IG_ORDERS Retail Administrator, Retailer User, Supplier Administrator, Supplier User Home ORCV_V_SPPP_ORD_NB ORDER_NO
Deliveries Grid P2_IG_DELIVERY_GRID Retail Administrator, Retailer User, Supplier Administrator, Supplier User Create or Edit PO ORCV_V_SPPP_ORD_NB ORDER_NO
References

Procure to Pay, Purchase Orders, also uses the Queries module to enable communications between retailer and supplier users, the details about Queries are available in the Supply Chain Hub Frameworks section. It also has dependencies from other modules batch jobs listed in POM Configuration that are documented in the Supply Chain Hub Frameworks section.

Operations

This section describes Purchase Order operations.

Integration by Modules

Figure 13-4 Procure to Pay Purchase Orders Integration by Module


Procure to Pay Purchase Orders Integration by Module

STEP DESCRIPTION
0 RSCH Data Access of MFCS data
1 Order No Reserve calls MFCS Services with a request to reserve Order No.
2 PO Induction Java Services checks if Procure to Pay has purchase orders to be published and produces ODS files to be consumed by MFCS PO Induction Job.
3 PO Induction Java Services sends produced files to Integration File Transfer.
4 Integration File Transfer publishes files to MFCS File Transfer Services (FTS) or MFCS shared folder (depending on configuration).
5 Procure to Pay calls Upload Download Java Service to transform files, depending on the request details, Upload Download Java Service might need to callback to Procure to Pay to get more details.
6 Event Alert Java Service checks if there are alerts to be triggered.
Reference

For operational details on integration and order reserve services, refer to the Supply Chain Hub Frameworks section.

Materialized Views Refresh Detail

This section describes Materialized Views Refresh Details.

ORCV_MV_SPPP_DASH_ALL_PO
Parameter Description Value
Result Synonym Synonym name pointing to the latest result table. ORCV_MV_SPPP_DASH_ALL_PO
Result Table A Name of _A result table. ORCV_SPPP_DASH_ALL_PO_A_R
Result Table B Name of _B result table. ORCV_SPPP_DASH_ALL_PO_B_R
Source View View used to refresh the result tables. ORCV_V_SPPP_DASH_ALL_PO_R
Driving View View used to distribute the refresh of result tables. ORCV_V_SPPP_DASH_ALL_PO_RC
Pre-Processor Pre-process procedure to execute, if applicable.

ORCV_COMMON_MV_REFRESH.

COMMON_PRE_PROCESSOR

Check Function Check function to validate if there is a need to refresh or if there are any batch dependencies. NA
Preserve Data Flag to decide if the data needs to be preserved until the next run cycle. Y
Restart Indicator Flag to indicate if restart is allowed or not. N
Max Concurrent Threads The maximum concurrent threads to refresh result tables. 4
Filter Fields Column(s) to distribute the refresh of result tables. DEPT, SUPPLIER
ORCV_MV_SPPP_DASH_PO_NEW
Parameter Description Value
Result Synonym Synonym name pointing to the latest result table. ORCV_MV_SPPP_DASH_PO_NEW
Result Table A Name of _A result table. ORCV_SPPP_DASH_PO_NEW_A_R
Result Table B Name of _B result table. ORCV_SPPP_DASH_PO_NEW_B_R
Source View View used to refresh the result tables. ORCV_V_SPPP_DASH_PO_NEW_R
Driving View View used to distribute the refresh of result tables. ORCV_V_SPPP_DASH_PO_NEW_RC
Pre-Processor Pre-process procedure to execute, if applicable.

ORCV_COMMON_MV_REFRESH.

COMMON_PRE_PROCESSOR

Check Function Check function to validate if there is a need to refresh or if there are any batch dependencies. NA
Preserve Data Flag to decide if the data needs to be preserved until the next run cycle. Y
Restart Indicator Flag to indicate if restart is allowed or not. N
Max Concurrent Threads The maximum concurrent threads to refresh result tables. 4
Filter Fields Column(s) to distribute the refresh of result tables. DEPT, SUPPLIER
ORCV_MV_SPPP_DASH_PO_PENDING
Parameter Description Value
Result Synonym Synonym name pointing to the latest result table. ORCV_MV_SPPP_DASH_PO_PENDING
Result Table A Name of _A result table. ORCV_SPPP_DASH_PO_PENDING_A_R
Result Table B Name of _B result table. ORCV_SPPP_DASH_PO_PENDING_B_R
Source View View used to refresh the result tables. ORCV_V_SPPP_DASH_PO_PENDING_R
Driving View View used to distribute the refresh of result tables. ORCV_V_SPPP_DASH_PO_PENDING_RC
Pre-Processor Pre-process procedure to execute, if applicable.

ORCV_COMMON_MV_REFRESH.

COMMON_PRE_PROCESSOR

Check Function Check function to validate if there is a need to refresh or if there are any batch dependencies. NA
Preserve Data Flag to decide if the data needs to be preserved until the next run cycle. Y
Restart Indicator Flag to indicate if restart is allowed or not. N
Max Concurrent Threads The maximum concurrent threads to refresh result tables. 4
Filter Fields Column(s) to distribute the refresh of result tables. DEPT, SUPPLIER
ORCV_MV_SPPP_DASH_PO_QTY_L5W
Parameter Description Value
Result Synonym Synonym name pointing to the latest result table. ORCV_MV_SPPP_DASH_PO_QTY_L5W
Result Table A Name of _A result table. ORCV_SPPP_DASH_PO_QTY_L5W_A_R
Result Table B Name of _B result table. ORCV_SPPP_DASH_PO_QTY_L5W_B_R
Source View View used to refresh the result tables. ORCV_V_SPPP_DASH_PO_QTY_L5W_R
Driving View View used to distribute the refresh of result tables. ORCV_V_SPPP_DASH_PO_QTY_L5W_RC
Pre-Processor Pre-process procedure to execute, if applicable.

ORCV_COMMON_MV_REFRESH.

COMMON_PRE_PROCESSOR

Check Function Check function to validate if there is a need to refresh or if there are any batch dependencies. NA
Preserve Data Flag to decide if the data needs to be preserved until the next run cycle. Y
Restart Indicator Flag to indicate if restart is allowed or not. N
Max Concurrent Threads The maximum concurrent threads to refresh result tables. 4
Filter Fields Column(s) to distribute the refresh of result tables. DEPT, SUPPLIER
ORCV_MV_SPPP_DASH_PO_WAIT_ASN
Parameter Description Value
Result Synonym Synonym name pointing to the latest result table. ORCV_MV_SPPP_DASH_PO_WAIT_ASN
Result Table A Name of _A result table. ORCV_SPPP_DASH_PO_WAIT_ASN_A_R
Result Table B Name of _B result table. ORCV_SPPP_DASH_PO_WAIT_ASN_B_R
Source View View used to refresh the result tables. ORCV_V_SPPP_DASH_PO_WT_ASN_R
Driving View View used to distribute the refresh of result tables. ORCV_V_SPPP_DASH_PO_WT_ASN_RC
Pre-Processor Pre-process procedure to execute, if applicable.

ORCV_COMMON_MV_REFRESH.

COMMON_PRE_PROCESSOR

Check Function Check function to validate if there is a need to refresh or if there are any batch dependencies. NA
Preserve Data Flag to decide if the data needs to be preserved until the next run cycle. Y
Restart Indicator Flag to indicate if restart is allowed or not. N
Max Concurrent Threads The maximum concurrent threads to refresh result tables. 4
Filter Fields Column(s) to distribute the refresh of result tables. DEPT, SUPPLIER
ORCV_MV_SPPP_DASH_PO_WAIT_DOC
Parameter Description Value
Result Synonym Synonym name pointing to the latest result table. ORCV_MV_SPPP_DASH_PO_WAIT_DOC
Result Table A Name of _A result table. ORCV_SPPP_DASH_PO_WAIT_DOC_A_R
Result Table B Name of _B result table. ORCV_SPPP_DASH_PO_WAIT_DOC_B_R
Source View View used to refresh the result tables. ORCV_V_SPPP_DASH_PO_WT_DOC_R
Driving View View used to distribute the refresh of result tables. ORCV_V_SPPP_DASH_PO_WT_DOC_RC
Pre-Processor Pre-process procedure to execute, if applicable.

ORCV_COMMON_MV_REFRESH.

COMMON_PRE_PROCESSOR

Check Function Check function to validate if there is a need to refresh or if there are any batch dependencies. NA
Preserve Data Flag to decide if the data needs to be preserved until the next run cycle. Y
Restart Indicator Flag to indicate if restart is allowed or not. N
Max Concurrent Threads The maximum concurrent threads to refresh result tables. 4
Filter Fields Column(s) to distribute the refresh of result tables. DEPT, SUPPLIER
ORCV_MV_SPPP_DASH_PO_WAIT_REV
Parameter Description Value
Result Synonym Synonym name pointing to the latest result table. ORCV_MV_SPPP_DASH_PO_WAIT_REV
Result Table A Name of _A result table. ORCV_SPPP_DASH_PO_WAIT_REV_A_R
Result Table B Name of _B result table. ORCV_SPPP_DASH_PO_WAIT_REV_B_R
Source View View used to refresh the result tables. ORCV_V_SPPP_DASH_PO_WT_REV_R
Driving View View used to distribute the refresh of result tables. ORCV_V_SPPP_DASH_PO_WT_REV_RC
Pre-Processor Pre-process procedure to execute, if applicable.

ORCV_COMMON_MV_REFRESH.

COMMON_PRE_PROCESSOR

Check Function Check function to validate if there is a need to refresh or if there are any batch dependencies. NA
Preserve Data Flag to decide if the data needs to be preserved until the next run cycle. Y
Restart Indicator Flag to indicate if restart is allowed or not. N
Max Concurrent Threads The maximum concurrent threads to refresh result tables. 4
Filter Fields Column(s) to distribute the refresh of result tables. DEPT, SUPPLIER
ORCV_MV_SPPP_PO_LAST_REV
Parameter Description Value
Result Synonym Synonym name pointing to the latest result table. ORCV_MV_SPPP_PO_LAST_REV
Result Table A Name of _A result table. ORCV_SPPP_PO_LAST_REV_A_R
Result Table B Name of _B result table. ORCV_SPPP_PO_LAST_REV_B_R
Source View View used to refresh the result tables. ORCV_V_SPPP_PO_LAST_REV_R
Driving View View used to distribute the refresh of result tables. ORCV_V_SPPP_PO_LAST_REV_RC
Pre-Processor Pre-process procedure to execute, if applicable.

ORCV_COMMON_MV_REFRESH.

COMMON_PRE_PROCESSOR

Check Function Check function to validate if there is a need to refresh or if there are any batch dependencies. NA
Preserve Data Flag to decide if the data needs to be preserved until the next run cycle. Y
Restart Indicator Flag to indicate if restart is allowed or not. N
Max Concurrent Threads The maximum concurrent threads to refresh result tables. 4
Filter Fields Column(s) to distribute the refresh of result tables. SUPPLIER
ORCV_MV_SPPP_PO_REJ_CANCEL
COLUMN DESCRIPTION VALUE
Result Synonym Name of the synonym pointing to the result table. ORCV_MV_SPPP_PO_REJ_CANCEL
Result Table A Name of _A result table. ORCV_ SPPP_PO_REJ_CANCEL_A_R
Result Table B Name of _B result table. ORCV_ SPPP_PO_REJ_CANCEL_B_R
Source View The View contains business logic to be used to populate the result table. ORCV_V_ SPPP_PO_REJ_CANCEL_R
Driving View This field contains the view to distribute the refresh process. ORCV_ SPPP_PO_REJ_CANCEL_RC
Pre-Processor Name of the pre-process procedure if applicable.

ORCV_COMMON_MV_REFRESH.

COMMON_PRE_PROCESSOR

Check Function Name of the check function to validate if there is a need to refresh or if there are any batch dependencies. NA
Preserve Data Flag to decide if the data needs to be preserved until the next run cycle. Y
Restart Indicator Flag to indicate if to allow restart batch processor or not. N
Max Concurrent Threads This field contains the maximum concurrent threads that created the record. 4
Filter Fields Column name of the view to be used for threading. SUPPLIER
ORCV_MV_SPPP_PO_TOTALS
Parameter Description Value
Result Synonym Synonym name pointing to the latest result table. ORCV_MV_SPPP_PO_TOTALS
Result Table A Name of _A result table. ORCV_SPPP_PO_TOTALS_A_R
Result Table B Name of _B result table. ORCV_SPPP_PO_TOTALS_B_R
Source View View used to refresh the result tables. ORCV_V_SPPP_PO_TOTALS_R
Driving View View used to distribute the refresh of result tables. ORCV_V_SPPP_PO_TOTALS_RC
Pre-Processor Pre-process procedure to execute, if applicable.

ORCV_COMMON_MV_REFRESH.

COMMON_PRE_PROCESSOR

Check Function Check function to validate if there is a need to refresh or if there are any batch dependencies. NA
Preserve Data Flag to decide if the data needs to be preserved until the next run cycle. Y
Restart Indicator Flag to indicate if restart is allowed or not. N
Max Concurrent Threads The maximum concurrent threads to refresh result tables. 4
Filter Fields Column(s) to distribute the refresh of result tables. ORDER_NO

Shipments

This section describes the Shipments features.

Implementation Overview

Procure to Pay, Shipments, will allow retailers and suppliers to create and maintain purchase ASNs.

Status Workflow

Figure 13-5 Shipments Status Workflow


Shipments Status Workflow

Shipments follow a workflow path, and the status can change depending on:

  • The user permissions
  • The status of the Shipment

Shipment Status:

  • New – New is the initial status while creating the Shipment in SPCH, this status is only an interim status and it is not possible to save a shipment in this status.
  • Approved – This status is used once a Shipment is submitted and integrated into MFCS. Whenever updates are made to the Shipment it remains in Approved Status.
  • Cancelled – Cancelled status is used when the shipment is cancelled in Procure to Pay.
  • Received – This status is shown once the Shipment has been received in MFCS.
Integration High Level

Figure 13-6 Procure to Pay Shipments Integration Overview

Procure to Pay Shipments Integration Overview

Note:

Shipments Java Service integration via RIB-EXT is an optional flow to integrate with SIOCS or WMS that requires enabling from the configuration. For more details on this process, see the Supply Chain Hub Frameworks section.

Configuration

This section describes configurations.

POM Configuration

Batch scheduler details with all batches, dependencies and frequencies can be downloaded following the steps in the Supply Chain Hub Frameworks section.

Schedule Overview

Figure 13-7 Procure to Pay Shipments Batch Schedule Overview

Procure to Pay Shipments Batch Schedule Overview
Other implementation Considerations

This section describes implementation considerations.

Custom Validations

The module performs validations by implementing Custom Validation Groups of the Custom Validations Framework described in the Supply Chain Hub Frameworks section. The groups listed below can be used to add Custom Validations for Purchase Orders.

Group ID Executed When
SPPP_ASN_CANCEL Shipment is cancelled
SPPP_ASN_SUBMIT Shipment is created or updated
Materialize Views

This application requires some results to be materialized in tables using the Materialized View Framework described in the Supply Chain Hub Frameworks section, below is the list for this application. Materialized views used in Procure to Pay, Purchase Orders, are listed in this section.

ORCV_MV_SPPP_DASH_OVD_UNSHIP

Materialize View to support Supply Chain Hub dashboard “Overdue Commitment (Units) - Top 5” showing Purchase Orders without shipments by department that are expected to be already shipped.

Pre-Dependencies: None

Post-Dependencies: None

Frequency: Ad-hoc.

ORCV_MV_SPPP_DASH_OVD_SHIP_Q

Materialize View to support Supply Chain Hub dashboard showing Purchase Orders with shipments with quantities remaining.

Pre-Dependencies: None

Post-Dependencies: None

Frequency: Ad-hoc.

Codes

Certain operations require codes to define the options available at system level. Below you can find the list of code types available.

The codes are defined in the ORCV_CODE_HEAD and ORCV_CODE_DETAIL tables.

CODE TYPE CODE TYPE DESCRIPTION
ASST Shipment status.
ASRC Shipment reason codes
Templates

This section describes templates.

Template SPPP ASNIN Data

Table 13-5 Template Key: SPPP_ASNIN_DATA

ACTION TYPE ROLE NAME
Download ORCV_SPPP_ASN_APPR_JOB
Download ORCV_SPPP_ASN_VIEW_JOB
Download Blank ORCV_SPPP_APP_JOB
Upload ORCV_SPPP_ASN_APPR_JOB

Table 13-6 ASN Worksheet

ACTION STATUS MANDATORY CELLS / FIELDS NOTES
Create New

Action,

ASN,

Supplier,

To Location Type,

To location,

Shipment Date,

Estimated Arrival Date

Creates an ASN with approved status.
Update Approve

Action,

ASN,

Supplier,

To Location Type,

To location,

Shipment Date,

Estimated Arrival Date

The action needs to be “Update” at the ASN Container worksheet even if the update is only at the container or item level.

Updates the ASN.

Cancel Approve

Action,

ASN,

Supplier,

To Location Type,

To location,

Shipment Date,

Estimated Arrival Date

Cancel an ASN.

Table 13-7 ASN Container Worksheet

ACTION STATUS MANDATORY CELLS / FIELDS NOTES
Create New

Action,

ASN,

Container

Adds container to the ASN.
Update Approve

Action,

ASN,

Container

The action needs to be “Update” in the ASN worksheet even if the update is only at the container level.

Updates the container.

Cancel Approve

Action,

ASN,

Container

Removes all quantities for the items associated with the container.

Table 13-8 ASN Items Worksheet

ACTION STATUS MANDATORY CELLS / FIELDS NOTES
Create New

Action,

ASN,

Order No,

Item,

Description,

Shipped Quantity,

Received Quantity

Adds items to the ASN.
Update Approve

Action,

ASN,

Order No,

Item,

Description,

Shipped Quantity,

Received Quantity

The action needs to be “Update” in the ASN worksheet and ASN Container worksheet if the item is associated with a container even if the update is only at the item level.
Cancel Approve

Action,

ASN,

Order No,

Item,

Description,

Shipped Quantity,

Received Quantity

The item quantity is adjusted to 0. If the remaining quantity for the ASN is null the cancel action should be done at ASN worksheet level.
Codes

Certain operations require codes to define the options available at system level. Below you can find the list of code types available.

The codes are defined in the ORCV_CODE_HEAD and ORCV_CODE_DETAIL tables.

CODE TYPE CODE TYPE DESCRIPTION
ASAC Shipments Actions
ASST Shipment Status
Interactive Grid Additional Columns

This application supports adding additional fields to the Interactive Grids by using the Interactive Grid Additional Columns functionality described in the Supply Chain Hub Frameworks section.

The Interactive Grids that support this functionality are listed below:

Interactive Grid Grid ID User Types Page Non Based View Entity Primary Key
Shipments Dashboard Grid P1_IG_SHIPMENTS Retail Administrator, Retailer User, Supplier Administrator, Supplier User Home ORCV_V_SPPP_ASN_NB ASN_NO
Purchase Orders Grid P3_IG_PO Retail Administrator, Retailer User, Supplier Administrator, Supplier User Create or Edit ASN ORCV_V_SPPP_ASN_NB ASN_NO
References

Procure to Pay, Shipments, also uses the Queries module to enable communication between retailer and supplier users, details about Queries are available in the Supply Chain Hub Frameworks section. It also has dependencies from other modules batch jobs listed in POM Configuration that are documented in the Supply Chain Hub Frameworks section.

Operations

This section describes operations.

Integration by Module

Figure 13-8 Procure to Pay Shipments Integration by Module

Procure to Pay Shipments Integration by Module
STEP DESCRIPTION
0 RSCH Data Access of MFCS data
1 Shipments Java Services checks if Procure to Pay has shipments to be published
2 If there are ASNin to be published, Shipments Java Services sends to MFCS via RIB-EXT REST
3 Procure to Pay calls Upload Download Java Service to transform files, depending on the request details, Upload Download Java Service might need to callback to Procure to Pay to get more details.
4 Event Alert Java Service checks if there are alerts to be triggered.

Reference

The Shipments ASNIN integration service will support the integration of ASNINs managed in the Procure to Pay module into MFCS via RIB-EXT REST. For more details on this process, consult the Supply Chain Hub Frameworks section.

Materialized Views Refresh Detail

This section describes the Materialized Views Refresh Details for Shipments.

ORCV_MV_SPPP_DASH_OVD_SHIP_Q
Parameter Description Value
Result Synonym Synonym name pointing to the latest result table. ORCV_MV_SPPP_DASH_OVD_SHIP_Q
Result Table A Name of _A result table. ORCV_SPPP_DASH_OVD_SHIP_Q_A_R
Result Table B Name of _B result table. ORCV_SPPP_DASH_OVD_SHIP_Q_B_R
Source View View used to refresh the result tables. ORCV_V_SPPP_DASH_OVD_SHIP_Q_R
Driving View View used to distribute the refresh of result tables. ORCV_V_SPPP_DASH_OVD_SHIP_Q_RC
Pre-Processor Pre-process procedure to execute, if applicable.

ORCV_COMMON_MV_REFRESH.

COMMON_PRE_PROCESSOR

Check Function Check function to validate if there is a need to refresh or if there are any batch dependencies. NA
Preserve Data Flag to decide if the data needs to be preserved until the next run cycle. Y
Restart Indicator Flag to indicate if restart is allowed or not. N
Max Concurrent Threads The maximum concurrent threads to refresh result tables. 4
Filter Fields Column(s) to distribute the refresh of result tables. DEPT, SUPPLIER
ORCV_MV_SPPP_DASH_OVD_UNSHIP
Parameter Description Value
Result Synonym Synonym name pointing to the latest result table. ORCV_MV_SPPP_DASH_OVD_UNSHIP
Result Table A Name of _A result table. ORCV_SPPP_DASH_OVD_UNSHIP_A_R
Result Table B Name of _B result table. ORCV_SPPP_DASH_OVD_UNSHIP_B_R
Source View View used to refresh the result tables. ORCV_V_SPPP_DASH_OVD_UNSHIP_R
Driving View View used to distribute the refresh of result tables. ORCV_V_SPPP_DASH_OVD_UNSHIP_RC
Pre-Processor Pre-process procedure to execute, if applicable.

ORCV_COMMON_MV_REFRESH.

COMMON_PRE_PROCESSOR

Check Function Check function to validate if there is a need to refresh or if there are any batch dependencies. NA
Preserve Data Flag to decide if the data needs to be preserved until the next run cycle. Y
Restart Indicator Flag to indicate if restart is allowed or not. N
Max Concurrent Threads The maximum concurrent threads to refresh result tables. 4
Filter Fields Column(s) to distribute the refresh of result tables. DEPT, SUPPLIER

Finance Documents

This section describes the Finance Documents features.

Implementation Overview

Procure to Pay, Purchase Orders, will allow retailers and suppliers to create and maintain financial documents.

Status Workflow

Figure 13-9 Procure to Pay Finance Documents Status Workflow


Procure to Pay Finance Documents Status Workflow

Finance Documents follow a workflow path, and the status can change depending on:
  • The user permissions
Finance Document Status:
  • New – New is the initial status while creating the Document in SPCH, this status is only an interim status and is not possible to save a Finance Document in this status.
  • Approved – This status is used once a Finance Document is submitted and integrated into IMCS.
  • Discrepancies – This status is used if any discrepancies are found during the matching process in IMCS.
  • Cancelled – Cancelled status is used if the Finance Document is cancelled in IMCS

Integration High Level

Figure 13-10 Procure to Pay Finance Documents Integration Overview


Procure to Pay Finance Documents Integration Overview

Configuration

This section describes configurations.

POM Configuration

Batch scheduler details with all batches, dependencies and frequencies can be downloaded following the steps in the Supply Chain Hub Frameworks section.

Schedule Overview

Figure 13-11 Procure to Pay Finance Documents Batch Schedule Overview


Procure to Pay Finance Documents Batch Schedule Overview

Other Cloud Services Configuration

This section describes implementation details that must be reviewed from an Oracle Retail Merchandising System perspective.

System Options

MFCS System Option LOCALIZATION_CONFIG_OPTIONS.DEFAULT_TAX_TYPE defines the default tax type used for Procure to Pay, Finance Documents.

Other implementation Considerations

This section describes implementation considerations.

Custom Validations - Finance Documents

The module performs validations by implementing Custom Validation Groups of the Custom Validations Framework described in the Supply Chain Hub Frameworks section. The groups listed below can be used to add Custom Validations for Finance Documents.

Group Id Executed When
SPPP_FINDOC_SUBMIT Financial Document is created
Codes

Certain operations require codes to define the options available at system level. Below you can find the list of code types available.

The codes are defined in the ORCV_CODE_HEAD and ORCV_CODE_DETAIL tables.

CODE TYPE CODE TYPE DESCRIPTION
DOCC Finance Document – Doc types, create mode
DOCV Finance Document – Doc types, view mode
FDST Finance Documents status.
Templates

This section describes templates.

Template SPPP Finance Document Data

One of these templates will be active, according to the configuration that exists in the MFCS for the default tax type.

Table 13-9 Templates

TEMPLATE KEY STATUS
SPPP_DOC_SVAT_DATA

Active (if MFCS system option for default tax type is SVAT)

Inactive (if MFCS system option for default tax type is different than SVAT)

SPPP_DOC_SALES_DATA

Active (if MFCS system option for default tax type is SALES)

Inactive (if MFCS system option for default tax type is different than SALES)

SPPP_DOC_GTS_DATA

Active (if MFCS system option for default tax type is GTS)

Inactive (if MFCS system option for default tax type is different than GTS)

Table 13-10 Template Key: SPPP_DOC_SVAT_DATA or SPPP_DOC_SALES_DATA or SPPP_DOC_GTS_DATA

ACTION TYPE ROLE NAME
Upload ORCV_SPPP_FINDOC_APPR_JOB
Download Blank ORCV_SPPP_APP_JOB

Table 13-11 Template Worksheets

WORKSHEET KEY WORKSHEET NAME SEQUENCE
SPPP_DOCS Documents 1
SPPP_DOC_REFS Document References 2
SPPP_DOC_ITEMS Document Items 3
SPPP_DOC_VAT Document VAT 4
SPPP_DOC_ITEM_TAX Document Item Tax 4

Note:

In case MFCS default tax type equals ‘SVAT’ the SPPP_DOC_VAT worksheet is used, in case of ‘GTS’ SPPP_DOC_ITEM_TAX is used, otherwise none of the previous worksheets are used.
Codes

Certain operations require codes to define the options available at system level. Below you can find the list of code types available.

The codes are defined in the ORCV_CODE_HEAD and ORCV_CODE_DETAIL tables.

CODE TYPE CODE TYPE DESCRIPTION
FDAC Finance Document Actions
FDOR Finance Document reference type
Interactive Grid Additional Columns

This application supports adding additional fields to the Interactive Grids by using the Interactive Grid Additional Columns functionality described in the Supply Chain Hub Frameworks section.

The Interactive Grids that support this functionality are listed below:

Interactive Grid Grid ID User Types Page Non Based View Entity Primary Key
Invoices Dashboard Grid P1_IG_INVOICES Retail Administrator, Retailer User, Supplier Administrator, Supplier User Home ORCV_V_SPPP_DOC_NB DOC_ID, SUPPLIER
Purchase Orders Grid P4_IG_PO Retail Administrator, Retailer User, Supplier Administrator, Supplier User Create or Edit Document ORCV_V_SPPP_ORD_NB ORDER_NO
Purchase Orders/ Return to Vendor Grid P4_IG_ORDRTV Retail Administrator, Retailer User, Supplier Administrator, Supplier User Create or Edit Document ORCV_V_SPPP_ORD_NB ORDER_NO
References

Procure to Pay, Finance Documents, also use the Queries module to enable communication between retailer and supplier users, details about Queries are available in the Supply Chain Hub Frameworks section. It also has dependencies from other modules batch jobs listed in POM Configuration that are documented in the Supply Chain Hub Frameworks section.

Operations

This section describes operations.

Integration by Module

Figure 13-12 Procure to Pay Finance Documents Integration by Module


Procure to Pay Finance Documents Integration by Module

STEP DESCRIPTION
0 RSCH Data Access of MFCS data
1 Finance Document Induction Java Services checks if Procure to Pay has documents to be published
2 Finance Document Induction Java Services sends produced files to Integration File Transfer.
3 Integration File Transfer publishes files to MFCS File Transfer Services (FTS) or MFCS shared folder (depending on configuration).
4 Procure to Pay calls Upload Download Java Service to transform files, depending on the request details, Upload Download Java Service might need to callback to Procure to Pay to get more details.
5 Event Alert Java Service checks if there are alerts to be triggered.

Reference

The EDI finance document injector service will support the integration of Invoices and Credit Notes managed in the Procure to Pay module into IMCS via induction batch. For more details on this process, please consult the Supply Chain Hub Frameworks section.