oracle shipping method

7/28/2019 Oracle shipping method

1/9

ORAtips

ORAtipsJournal

October2005

VolumeIIssue1

ORAtips.com ORAtips 2005 Klee Associates

Introduction: What is aStuck Line

All transactions that impact inven-tory will interace to the Oracle Inven-tory and Oracle Financial modules.The transactions will occur in OraclePurchasing, Oracle Order Manage-ment, Oracle Work In Progress (WIP),to name a ew. I the transaction inor-

mation is not interaced properly, thetransactions will be stuck in the inter-ace table. The stuck lines will pre-vent the Oracle Inventory account-ing period rom closing as shown inFigure 1 using the navigation path:Oracle Inventory > Accounting CloseCycle > Inventory Accounting Period> (Button) Pending.

This article will discuss how toclear stuck shipping lines.

How to Identiy StuckShipping Lines

During the shipping executiprocess and ater the shipping linare ship conrmed, the shippiinormation will be interaced to tOracle Order Management and Orcle Inventory modules via the Intace Trip Stop - SRS concurre

program.

I the Interace Trip Stop SRconcurrent program nishes succeully, the shipping line status wchange rom shipped to intaced. Hence, shipped status is interim status. I the shipping linstatus remains shipped, we cthese lines stuck shipping lines shown in Figure 2.

Editors Note: Most o you areprobably amiliar with Oracles 11iShipping Execution unctionality. Ashipping delivery-based system, cus-tomers typically use it to track trips,i.e., delivery lines that are scheduledto be shipped in a specifc vehicle ona specifc date by a specifc carrierdeparting rom a specifc location.

What happens when the shippinglines become stuck in an interacetable? Leaving them there is notan option because o the impact toOracle Inventorys accounting peri-ods. Purging them is not an optionbecause this is business critical data.

Scott Ma, our Manuacturing expert,has written an inormative articleintended to help you realize the ullvalue o this unctionality and howto trouble-shoot stuck transactions.

Scott begins with the basics how toanalysis your transactions using theInterace Trip Stop concurrent pro-cess, and then goes on to list commoncauses and solutions that account

or most issues. Even experiencedusers will pick up some useul point-ers with this introductory article.

Oracle 11i Shipping Execution

Interface Trip Stop Trouble ShootingBy Scott M

4on Order Management - Shipping

Figure 1 Inventory Accounting Periods and Pending Transactions

If the transaction

information is not

interfaced properly,

the transactions

will be stuck in the

inter-face table.


2/9

ORAtips

ORAtipsJournal

October2005

VolumeIIssue1


The stuck lines will cause inven-tory inaccuracies. Each month end,all pending transactions must becleared in order to keep accounting

and inventory inormation in-sync.

Stuck Shipping LinesTrouble Shooting Analysis

Once you have identied shippinglines that are stuck, the next step is themost challenging part. You are goingto determine why they are stuck. Themost useul inormation you can useis the Interace Trip Stop - SRSconcurrent request log le. But bewarned, you will need patience; thisis a long log le. It is typically 20-

30 pages. You have to read throughit and, most o the time, the inor-mation that will help you identiy theissue is just a ew sentences.

Step 1 Submit the Interace TripStop concurrent program

The Oracle 11i shipping executionprocess is delivery-based shipping;thereore you will need to run theInterace Trip Stop - SRS concur-

rent program against the deliverythat is stuck, as shown in Figure 3.

Step 2 Obtain the concurrent

request log le as shown in Figure 4.

Tip: Write down the InteraTrip Stop concurrent request when you submit the progra

This will make it easier to nd oncompleted.

How to Clear StuckShipping Lines

There are many sources that cotribute to stuck shipping lines. Thinclude, but are not limited to:

No Remote Transaction Manag

Subinventory has been denas Allow Reservation or AT

items

Negative price not allowed

Not enough on hand quantitystaging subinventory, negatbalances not allowed

ORA-20002: 3133: Activinstance SHIP_LINE is notnotied activity. The workfownot in the expected status.


Figure 2 Stuck Shipping Lines

Figure 3 Submit the Interface Trip Stop - SRS Concurrent Program


3/9

ORAtips

ORAtipsJournal

October2005

VolumeIIssue1


Scenario 1 No RemoteTransaction ManagerSymptom:When you review the Interace TripStop log le, the error messageNo Remote Transaction Manageroccurs.

Cause:While the concurrent program Inter-ace Trip Stop was running, or somereason, it was interrupted; those linesthen are stuck in the interace table.

SolutionStep 1 Clear Pending Transactionsas shown in Figures 5a and 5b, usingthe navigation path: Oracle Invento-ry > Transactions > Pending Trans-actions.

Step 2 Clear the Transaction OpenInterace as shown in Figures 6a and6b using the navigation path: OracleInventory > Transactions > Transac-tion Open Interace.

Step 3 Resubmit the Interace TripStop - SRS concurrent program orthe stuck delivery (Figure 3) usingthe Navigation Path: Oracle OrderManagement > Shipping > Interaces> Run.


Figure 4 Completed Interface Trip StopConcurrent Program Request ID and View Log

Figure 5b ClearPending Transactions

Figure 5a FindPending Transaction


4/9

ORAtips

ORAtipsJournal

October2005

VolumeIIssue1


Scenario 2 Subinventoryhas been dened as AllowReservation or ATO items

Symptom:When you review the Interace TripStop log le, the error message

Subinventory is Not AllowReservation occurs.

Cause:For ATO items, the staging subin-ventory has been dened as AllowReservation.

Solution:

Most o the time, the staging subin-ventory is set to Allow Reservation.I you set subinventory to Not AllowReservation, it will cause an errorwhen the Interace Trip Stop - SRSconcurrent program is run or ATOitems.

Step 1 Change the old staging sub-inventory to Allow Reservation asshown in Figure 7 using the naviga-tion path: Oracle Inventory > Setup

> Organization > Subinventory.

Step 2 Resubmit the Interace TripStop - SRS concurrent program orthe stuck delivery (Figure 3) usingthe navigation path: Oracle OrderManagement > Shipping > Interaces> Run

Step 3 Change the old staging sub-inventory back to Not Allow Reser-vation

Step 4 Find the move orders cre-ated or the old staging subinventoryand back order those move orders asshown in Figure 8.


Figure 6a Find Interface Transactions

Figure 6b Clear Interface Transactions


5/9

ORAtips

ORAtipsJournal

October2005

VolumeIIssue1


Figure 7 SubInventories

Figure 8 Find Move Orders



6/9

ORAtips

ORAtipsJournal

October2005

VolumeIIssue1


Scenario 3 Not AllowNegative PriceSymptom: When you review the

Interace Trip Stop log le, theerror message

Not Allow Negative Priceoccurs.

Cause: There are two proles thatcause this issue:

QP: Negative Pricing set to No

QP: Selling Price RoundingOptions: set to No = unrounded

list price + unrounded adj

In this scenario, we will place asales order with a price o zero.

Consequently, since QP: Sell-ing Price Rounding Options is setas No Rounding, when InteraceTrip Stop is run, it calculates theprice as - 0.0000xxx. But note,when QP: Negative Pricing is setto Not Allow Negative, it causes an

error.

Short Term SolutionStep 1 Set QP: Selling PriceRounding Options at the user level

to Individual: = round (list price) +round(adj) as shown in Figure 9.

Step 2 Resubmit the Interace TripStop - SRS concurrent program orthe stuck delivery using the naviga-tion path: Oracle Order Manage-ment > Shipping > Interaces > Run(Figure 3).

Long Term SolutionYou will need to coordinate with

all unctional areas related to OracleOrder Management, Oracle Shipping,Oracle Pricing, Oracle Inventory, andOracle Financial modules to reach

consensus.

Scenario 4 Not enoughon hand quantity in stag-ing subinventory, Negativebalances not allowedSymptom: When you review Inter-ace Trip Stop log le, the errormessage

Negative Balance is Not Allowedoccurs.

Cause: When the Interace TripStop SRS concurrent programruns, it will interace to the OracleInventory to update on hand quan-

tity and deduct shipped quantrom the staging subinventory or tshipped item. I there is not enouon hand quantity in staging subiventory, it will cause the line stuck

SolutionStep 1 Contact the business usto determine i there is enough hand quantity in the staging subiventory. I there is not, most o t

time it is because the business usehave manually moved them out the subinventory.

Step 2 Using the Subinventory Traner process, i an item was accidetally transerred out o the stagisubinventory, it can be transerrback. Figure 10 demonstrates thusing the navigation path: OraInventory > Transactions > Subiventory Transer.Figure 9 QP: Selling Price Rounding Option

Using the

Subinventory

Transfer process, if

an item was

accidentally

transferred out of

the staging

subinventory, it

can be transferred

back.



7/9

ORAtips

ORAtipsJournal

October2005

VolumeIIssue1


Alternatively you can use the CycleCount or Miscellaneous Receipt unc-tion.

Step 3 Resubmit the InteraceTrip Stop - SRS concurrent programrequest or the stuck delivery usingthe navigation path: Oracle OrderManagement > Shipping > Interaces> Run (Figure 3).

Scenario 5 Workfow is notin appropriate statusSymptom: When you review theInterace Trip Stop log le, theerror message ORA-20002: 3133:Activity instance SHIP_LINE is nota notied activity.... OR the work-fow is not in the expected statusmay occur.

Cause: Ater the sales order shipped, the sales order line statis still awaiting shipping. It shoube closed.

SolutionStep 1 You could try executing tsample script below to perormdata x, and then analyze the deble to identiy the root cause:

set server output on;

Declare

l_line_id NUMBER := &line_id;

l_org_id NUMBER;

l_count NUMBER;

l_result VARCHAR2(30);

l_le_val varchar2(200);

BEGIN

OE_DEBUG_PUB.DEBUG_ON;

OE_DEBUG_PUB.INITIALIZE;

l_le_val := OE_DEBUG_PUB.Set_Debug_Mode(FILE);

OE_DEBUG_PUB.SETDEBUGLEVEL(5);

dbms_output.put_line(The debug log is stored at : ||OE_DEBUG_PUB.G_DIR||/||OE_DEBUG_PUB.G_FILE);

dbms_output.put_line(Please capture the above debug log and send it to support/dev for investigation);

OE_Standard_WF.OEOL_SELECTOR

(p_itemtype => OEOL

,p_itemkey => to_char(l_line_id)

,p_actid => 12345

,p_funcmode => SET_CTX

,p_result => l_result

);

Figure 10 Subinventory Transfer Window



8/9

ORAtips

ORAtipsJournal

October2005

VolumeIIssue1


Step 3 Resubmit Interace TripStop - SRS concurrent program or

the stuck delivery using the naviga-tion path: Oracle Order Manage-ment > Shipping > Interaces > Run(Figure 3).

ConclusionPending Transactions (as in Fig-

ure 1) is the most common issue thatalmost every Oracle client will haveto conront during the rst 6-12months ollowing go live. It is also themost comprehensive issue, because

Oracle Purchasing, Oracle OrderManagement, Oracle Work In Prog-

ress (WIP), etc might cause it. Thereare literally hundreds o reasons thatwill cause the transaction pending/stuck to occur. This article primarilyaddresses issues or the Oracle OrderManagement - Shipping module.

Scott Ma Scott is a senior levOracle Consultant, who has t

years Oracle experience. His OraApplications implementation exprience includes R11.5.10, R11.5R11.5.3, and R10.7. He is one o tew Oracle consultants who knoboth Oracle manuacturing and dtribution areas. He is very strong acdemically as well. He has two Masdegrees with majors in IndustrManagement and Industrial Enneering. Scott may be contacted [email protected].

wf_engine.handleError(OEOL, l_line_id, SHIP_LINE, RETRY,null);

END;/

COMMIT;

DECLARE

l_line_id NUMBER := &line_id;

l_org_id NUMBER;

l_count NUMBER;

l_activity_id NUMBER;

l_result VARCHAR2(30);

BEGIN

OE_Standard_WF.OEOL_SELECTOR

(p_itemtype => OEOL

,p_itemkey => to_char(l_line_id)

,p_actid => 12345

,p_funcmode => SET_CTX

,p_result => l_result

);

select activity_id

into l_activity_id

from wf_item_activity_statuses_v

where item_type = OEOL

and activity_name = SHIP_LINE

and item_key = to_char(l_line_id)

and activity_status_code = ERROR;

wf_item_activity_status.create_status(OEOL,to_char(l_line_id),l_activity_id,wf_engine.eng_notified,wf_engine.engnull,SYSDATE,null);

End;

/

commit;



9/9

ORAtips

ORAtips

Journal

Journal

October2005

VolumeIIssue1

ORA i

The inormation on our website and in our publications is the copyrighted work o Klee Associates, Inc. and is owned by Klee Associates, Inc. NO WARRANTY: documentation is delivered as is, and Klee Associates, Inc. makes no warranty as to its accuracy or use. Any use o this documentation is at the risk o the user. Altho

we make every good aith eort to ensure accuracy, this document may include technical or other inaccuracies or typographical errors. Klee Associates, Inc. resethe right to make changes without prior notice. NO AFFILIATION: Klee Associates, Inc. and this publication are not afliated with or endorsed by Oracle CorporatOracle is a registered trademark o Oracle Corporation and/or its afliates. Klee Associates, Inc. is a member o the Oracle Partner Network

This article was originally published by Klee Associates, Inc., publishers of JDEtips and SAPtips.For training, consulting, and articles on JD Edwards or SAP, please visit our websites:www.JDEtips.com and www.SAPtips.com.

oracle shipping method

Documents