Shipping Execution - EBS (MOSC)

MOSC Banner

DSNO outbound file issue

edited Dec 16, 2018 4:00AM in Shipping Execution - EBS (MOSC) 3 commentsAnswered

We've recently found that our outbound DSNO flat files will contain an extra set of 5600-5790 lines. When these are encountered, our maps stop and truncated the ASN going to the customer.  We're looking for ways to map around this, but I'm wondering if it's a bug in the code.  Has anyone else encountered this issue, if so how was it resolved?  It seems it could be the way the shipment is getting processed but I do not know how to replicate the issue.

Normally, lines progress to 6000 then 7000-9000, then loop back to 5600 lines again.  We will see 5600 lines then 5600 lines start over (missing 6000-9000)

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

EBS Shipping Tags

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center