Procurement - EBS (MOSC)

MOSC Banner

Requisition Import: Why is deriving the SOURCE_ORGANIZATION_ID failing for some users?

edited Sep 16, 2015 10:09AM in Procurement - EBS (MOSC) 3 commentsAnswered

Concurrent program Requisition Import in EBS 11.5.10.2

Hello all,

we are importing Internal Requisitions via interface table po_requisitions_interface_all. We are setting AUTOSOURCE_FLAG = 'P' (partially derived). For all columns we are filling, see an example in attachment (requisitions_interface_all.xlsx).

When running the program Requisition Import, parameter Import Source is INTERFACE. Therefore, we are expecting that SOURCE_ORGANIZATION_ID is derived by the program. Sourcing rules for the items are set up.

Now, the Requisition Import always works fine for some users.

For other users, the Requisition Import constantly fails for exactly the same records inserted. For an example see the attachments (po_requisition_interface_all_83164681.xlsx, po_interface_errors_83164681.xlsx). The errors message that seems to address the root problem says "Source organization is missing or invalid. / Cause: The source organization is missing or invalid. The source organization is required if the source type is 'INVENTORY'. / Action: Enter a valid source type." (this message must be App-14624)

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center