My Oracle Support Banner

Automatic Attachment Are Re sequenced When Changed Ship To Address On Line Level. (Doc ID 1571750.1)

Last updated on AUGUST 27, 2021

Applies to:

Oracle Order Management - Version 12.1.3 and later
Information in this document applies to any platform.


On : 12.1.3 version, Product Utilities

Oracle Apps Version: 12.1.3

Problem Description/Question:
When user is trying to change the ship to address at line level in the sales
order, automatic attachment number is getting re sequenced.

Expect to retain the sequence number on an automatic attachment after
updating the ship to address on the sales order form.

Copy order #1 to order #2.
Open order #2, go to lines. See line 1.1
View attachments: see 7 attachment with seq number 10,20,30,40,50,60,70
Seq # 10-80 are reserved for BOM attachments.
At line item form, Action > Apply Automatic Attachment
View attachment: see new seq 80 "invoice", change 80 to 300, save
Re-query order and view attachment, see seq #300 "invoice".
  - note, cannot check "May be changed" box.
Change line 1.1 ship to address and save.
View attachment: see seq 80 "invoice" - Expect seq 300 "invoice"

 This is considered an issue for customer because Team center (third party
 system) pushes BOM attachment from Team center to Oracle OM, which is
 sequence from 10 to 99. The sequence # from 10 to 99 are reserved for Build
 of Materials (BOM) only. After changing the ship to address, sequence number
 300 is getting back again to next sequence number in the list of attachment
 (80). This will corrupt the BOM attachment, when ship to address is changed.




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.