Skip to content

EDIFACT transaction code

EDIFACT ORDCHG Purchase Order Change Request

EDIFACT ORDCHG Purchase Order Change Request: explore its business purpose, mapping identifiers, validation tests and 1 partner references across 1 listed channels.

Standard
EDIFACT
Code
ORDCHG
Partner references
1

Implementation guide

EDIFACT ORDCHG mapping and validation

EDIFACT ORDCHG Purchase Order Change Request is used when a buyer revises an existing order. Preserve original order, revision and affected line so the purchase-order change in your business system stays connected to the original document.

Use the version and implementation guide agreed with your trading partner to confirm required fields and responses.

Map records and test the business result
Document or decisionRecord and matching IDsWhat to test
Match the business record purchase-order change

original order, revision and affected line

  • Define which combination of original order, revision and affected line identifies one business record, its lines and any later revision.
Update the receiving system Processing the purchase-order change

ID assigned by the receiving system and processing result

  • Apply a change to the original order without duplicating it.
  • Test a cancellation after dispatch and route it for review.
Check the processing result Processing status for the purchase-order change

Original document reference and matching response

  • Reconcile the purchase-order change with the source after a timeout before sending it again. A lost response can occur after the destination has already processed the document.

How the related documents differ

Each message represents a different business event. Use shared references to connect the records while tracking each message’s outcome separately.

Implementation steps

  1. Choose the starting event and owner

    Decide which application acts when a buyer revises an existing order. Name the operational owner of the purchase-order change and the team that resolves rejected or ambiguous messages.

  2. Keep record IDs connected

    Map original order, revision and affected line. Confirm qualifiers, code lists, units and date/time meaning against the agreed EDIFACT version and partner guide. Preserve the source reference alongside any new destination identifier.

  3. Test failures before launch

    Run the failure cases in the mapping table against realistic purchase-order change data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate.

  4. Track every document to completion

    Record transport delivery and document validation separately from successful purchase-order change processing. Give unresolved errors an owner and check the receiving system before approving retries.

Go-live checklist

  • An approved ORDCHG sample and the agreed version and partner guide are available.
  • The mapping tests pass with realistic purchase-order change data.
  • Each submitted document can be traced through delivery, validation and processing in the receiving system.
  • Your team knows how to investigate and recover a rejected or timed-out purchase-order change without processing it twice.

Find your trading partner for EDIFACT ORDCHG

1 partner, 1 channel. Choose a channel to inspect its listed document reference and implementation context.

Catalog breakdown

Where EDIFACT ORDCHG Purchase Order Change Request appears in this catalog

The largest groups of classified ORDCHG catalog entries are in e-commerce & marketplaces.

By industry

  • e-commerce & marketplaces 1 channel
Partner entries with the most listed channels

FAQ

EDIFACT ORDCHG questions

What is EDIFACT ORDCHG Purchase Order Change Request used for?

ORDCHG is used when a buyer revises an existing order. It carries information for the purchase-order change. Match it to your business system using original order, revision and affected line.

Which partners list EDIFACT ORDCHG?

The directory on this page links 1 partner entries that list this message. Choose your partner and channel, then confirm which messages and versions your account requires.

What should I map for EDIFACT ORDCHG?

Start with original order, revision and affected line and the target purchase-order change. Define duplicate detection, allowed updates and response correlation before mapping individual fields. Use the partner guide to check required fields and their formats.

How should I test ORDCHG error handling?

Apply a change to the original order without duplicating it. Test a cancellation after dispatch and route it for review. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.

How does ORDCHG relate to other EDI messages?

EDIFACT ORDERS Purchase Order; EDIFACT ORDRSP Purchase Order Response are related documents linked from this page. Match these documents through their order, shipment or invoice references. Agree which response marks each business step as complete.

What is the difference between ORDCHG and ORDERS?

ORDCHG is used when a buyer revises an existing order. ORDERS is used when a buyer places an order. Each message represents a different business step. Keep their record references connected and track the processing result for each message.

Connect EDI to your business systems

See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout.