Related topics
- About purchase order acknowledgement
- About the Consolidated merged invoice functionality
- About the EANway method
This panel displays the existing trading partners. A trading partner is the overall customer for incoming/outgoing EDI messages and is contained within the EDI functionality as either the sending or receiving party.
Options
V/routines | Select this option to view the validation routines of the trading partner. |
Entities | Select this option to view the internal company brand of the trading partner. |
Labels | Select this option to specify whether labels are required for the item groups. |
P/routines | Select this option to view the CPO pre-edit routines of the trading partner. |
Selection fields
- Trading partner
- This column lists the existing trading partners, i.e. either the sending or receiving customer for EDI messages.
- Name
- This column lists the names of the trading partners.
- PVT
- Displays the price variance tolerance for the trading partner. It is only referred if the corresponding price variance routines are activated for the trading partner. Note: This field is set as 0.0200 dollars to ensure that the unit price is correct other than rounding issues.
- GNP
- Indicates if the incoming unit price is to be applied to the order lines. If NO, then the current system unit price will be applied (get new prices).
- ARH
- Indicates if the ASN will be held for review. If YES, it allows the creation of an ASN that is temporarily held for review before sending. As a result, manual integrity checks occur which is useful during the testing phase for a new trading partner or entity.
- SLSR
- Displays the minimum SLS (Service Level Support) percentage below which sales orders will not be created, in situations where the CPO is identified as a Replenishment order.
- SLSC
- Displays the minimum SLS (Service Level Support) percentage below which sales orders will not be created, in situations where the CPO is identified as a Catalogue order.
Work with trading partners (AUDD02204)
On this panel you add a new or maintain an existing trading partner.
- Trading partner
- Enter a code to identify the new trading partner that you are adding.
- Name
- Enter the full name of the trading partner.
- Price var tolerance
- Only applicable if the corresponding price variance routines are activated for the trading partner. Enter zero or a suitable dollar amount to avoid unnessary price rejections due to rounding or discount issues.
- Scanpack label type
- Enter the SSCC label format, from the Panel value control file, required for the trading partner.
- Adv date format
- Enter the advertised date format for the trading partner. Valid values are:
Code Description 0 Represents the YYMMDD date format. 1 Represents the DDMMYY date format. 2 Represents the DDMM date format. 9 Represents the Myer date format.
- S/pack val wgt/vol
- Indicate if the scan pack validation for weight/volume is required for the items. This field is used to freeze the CPO if:
- The items to be scanned do not resolve a non-zero weight and/or volume.
- The trading partner requires non-zero values in the subsequent ASN.
- Debtor
- Enter a code, from the Business partner file, that identifies the customer that payment is expected from.
DI orders ret o/ride
- Handler
- Enter the ID, from Work with signatures, of the employee responsible for handling the tasks related to the item.
- Order type
- Enter the order type.
- Currency
- Enter the currency, from Work with currencies, for the price of the item.
- Warehouse
- Enter a code, from Work with warehouses, indicating the warehouse to which the item belongs.
- Get new prices
- Indicate if the incoming unit price is to be applied to the order lines. If NO, then the current system unit price will be applied.
POC/POA
- POC change purp code
- Enter a purpose code to identify the EDI document should the trading partner send duplicate 850/ORDERS or 860/ORDCHG documents. The code indicates that the EDI document is a CHANGE request and assists in the suitable handling of the change.
- POC delete purp code
- Enter the purpose code indicating that the EDI document is a DELETE request.
- POA required
- Indicate if the purchase order acknowledgement is required to be sent to the customer. This field works in combination with the associated entity (Eligible for POA = YES/NO), since all the entities for the trading partner might not require a POA.
- POA model
- Indicate the format in which the purchase order acknowledgement is requested by the trading partner.
- EDI POA hold
- Indicate if review of the held EDI documents is to be done prior to sending them to the trading partner.
- Ignore SLS failure
- Indicate if the SLS (Service Level Support) failure is to be ignored prior to creation of the sales order.
- Hld CPO for SLS fail
- Indicate if the CPO is to be held for processing due to SLS failure. This field works in conjunction with the Ignore SLS failure field.
- Dlt exist sts 20 ord
- Indicate if all the orders below status 20 should be deleted.
ASN status codes
- Short shipment
- If the trading partner requires one ASN per CPO and vehicle, then enter the short shipment code as defined by the trading partner. If a CPO is greater than one vehicle, then separate ASNs are required. All ASNs must contain the short shipment code, except the last ASN. The last/final ASN will hold the complete shipment flag.
- Complete shipment
- If the trading partner requires complete shipment, then enter the complete shipment code as defined by the trading partner.
- Review hold
- Indicate if the ASN should be held for review. If YES, it allows the creation of an ASN that is temporarily held for review before sending. As a result, manual integrity checks occur which is useful during the testing phase for a new trading partner or entity.
Floor readiness
- Labels required
- Indicate if floor readiness labels are required. Such labels are used for customers that require each item to be supplied with price tickets in a fixed format. Note: This field works in conjunction with Retail price list. If floor readiness labels are not required, then the retail price list cannot be specified.
- Retail price list
- Indicate the retail price list that should be used for the trading partner. The values are defined in the Retail price lists table. Note: This field works in conjunction with Labels required. If floor readiness labels are not required, then the retail price list cannot be specified.
Work with trading partner, Copy (AUDD02205)
- Old trading partner
- Displays the existing trading partner you selected to copy.
- New trading partner
- Enter the new trading partner ID that you are creating.
Work with trading partner, Deletion (AUDD02208)
Work with trading partners (AUDD02211)
On this panel you continue to add or maintain information for a new or an existing trading partner.
Service level support
- Replenishment min%
- Only applicable if a CPO SLS code is specified. Enter a value between 1 and 100 indicating the minimum SLS percentage below which sales orders will not be created in instances where the CPO is identified as a replenishment order.
- Catalogue min%
- Enter a value between 1 and 100 indicating the minimum SLS percentage below which sales orders will not be created in instances where the CPO is identified as a catalogue order. If this field is left blank, then 100% is assumed.
- Calculation rule
- This field only applies if either of the Replenishment min% and Catalogue min% fields is completed. Enter one of the following codes to indicate which calculation rule should be used:
Code Description 1 Calculation based on number of lines filled. 2 Calculation based on unit quantity filled.
Sales order type override
This section enables you to specify the override sales order types for Crossdock, Direct to store, Warehouse and Blanket orders for both catalogue and replenishment orders. This feature will provide improved visibility of the sales orders. You can also indicate merge invoicing override for the Direct to store order type. The fields can be left blank.
Note: If the Crossdock sales order type is not entered, then the order type will be retrieved from the DI setup for the respective customer during the DI file build, if applicable.
Miscellaneous
- Consolidated M/Invc
- Indicate if the trading partner requires a consolidated merged invoice to be printed.
- Address 4 Suburb/St
- Indicate if the common output of the suburb/state on the SSCC label should be used for the trading partner. Valid values are:
Code Description YES Common output is required for SSCC labels. NO Different address formats will be used.
- SCM location alpha
- Indicate how the goods address numbers are represented on the SSCC labels and on the ASN. If YES, alphanumeric representation is used. If NO, only numeric representation is used.
- SSCC allow mult GTIN
- This field is currently not in use.
- Mrg inv selct warng
- When a request for merged invoice is made, a check is performed for all order lines on a CPO to avoid order lines from being held at an early stage and not qualifying for the merged invoice or single ASN. Valid values are:
Code Description YES The message is a warning. NO The message is an error.
- CPO auto mode
- Indicate if the automatic validation/sales order creation from the CPO EANwayORD data queue routine, per trading partner, should be allowed.
- CPO auto complete
- This field is currently not in use.
- Factory gate pricing
- This field is currently not in use.
- CPO hld for W/H proc
- Indicate if the CPO should be held from warehouse processing. If YES, then the CPO cannot be released to the warehouse for picking, pending review and CPO maintenance at pick list printing time.
- D/date driven CPO
- This field is currently not in use.
- Lead zero GTIN/ASN
- Indicate if a leading zero should be applied to outbound GTINs within an ASN. This is useful if the outbound GTIN is held on file because it contains less than 13 digits and the trading partner requires a 13-digit GTIN in the ASN.
Work with trading partners (AUDD02212)
On this panel you continue to add or maintain information for a new or an existing trading partner.
User defined
The fields in this section are completely user-defined. The ones displayed have been defined in the EANway application control file, in the Trading partner text section. You can use the fields as you wish. The information entered in the fields are for informational purposes only.
- Alpha 1-5
- Numeric 1-5
- Alpha flag 1-5