Scribd
Upload
19 views5 pages

ASN/Shipment Number Stuck in Technical Success Status in GIS Step by Step Process

Uploaded by

Manish Singh

The document provides steps to resolve an ASN/shipment number stuck in a technical success status in GIS. The steps include checking interface tables for errors, identifying and removing cancelled PO lines, clearing interface tables after backup, updating the status in GIS, retriggering from human task, and verifying successful processing.

Copyright:

© All Rights Reserved
Download as DOCX, PDF, TXT or read online from Scribd
Download as docx, pdf, or txt

ASN/Shipment Number Stuck in Technical Success Status in GIS Step by Step Process

Uploaded by

Manish Singh
19 views5 pages
The document provides steps to resolve an ASN/shipment number stuck in a technical success status in GIS. The steps include checking interface tables for errors, identifying and removing cancelled PO lines, clearing interface tables after backup, updating the status in GIS, retriggering from human task, and verifying successful processing.

Original Title

ASN

Copyright

© © All Rights Reserved

Available Formats

DOCX, PDF, TXT or read online from Scribd

Did you find this document useful?

Is this content inappropriate?

The document provides steps to resolve an ASN/shipment number stuck in a technical success status in GIS. The steps include checking interface tables for errors, identifying and removing cancelled PO lines, clearing interface tables after backup, updating the status in GIS, retriggering from human task, and verifying successful processing.

Copyright:

© All Rights Reserved
Download as DOCX, PDF, TXT or read online from Scribd
Download as docx, pdf, or txt
19 views5 pages

ASN/Shipment Number Stuck in Technical Success Status in GIS Step by Step Process

Uploaded by

Manish Singh
The document provides steps to resolve an ASN/shipment number stuck in a technical success status in GIS. The steps include checking interface tables for errors, identifying and removing cancelled PO lines, clearing interface tables after backup, updating the status in GIS, retriggering from human task, and verifying successful processing.

Copyright:

© All Rights Reserved
Download as DOCX, PDF, TXT or read online from Scribd
Download as docx, pdf, or txt
You are on page 1/ 5

ASN/Shipment Number Stuck in Technical Success Status in GIS

Step by Step Process:


1) Check the transaction in GIS ASN tab

Find the err note like below:

2) Check the RCV_Transactions_interface (RTI ) table with the shipment number/ ASN number
provided, it must be in ERROR

3) Check the PO_Interface_errors table with the Batch ID which is the Group ID column of RTI.
We can find the err like,“PO Shipment line =# is cancelled”

4) We need to take those PO cancelled lines out from the list of Pos under that ASN
And inform business(i.e Juliana Peixoto)

Below query to find out the above list:

** put the shipment numbers as required**

alter session set current_schema = apps;/

select PHA.segment1 "PO NO.",pha.attribute1,pla.attribute1,


PLA.ITEM_ID,
PLA.line_num "LINE NO.",
PLLA.shipment_num "SHIPMENT NO.",
PLLA.quantity "QTY",
PLLA.quantity_received"QTY RCVD",
NVL (PLLA.quantity, 0) - NVL (PLLA.quantity_received, 0) "QTY DUE",
PLLA.quantity_cancelled "QTY CANCEL", PLLA.QTY_RCV_TOLERANCE "OVER RCPT TOLE.",
PLLA.PRICE_OVERRIDE "UNIT PRICE", PHA.AUTHORIZATION_STATUS "PO HEADER STATUS",
PLA.CLOSED_CODE,
PLLA.CLOSED_CODE "SHPMNT LINE CLOSURE STATUS",
decode(PLLA.APPROVED_FLAG,'Y','Approved','N','Not Approved','R','Requires
Approval',PLLA.approved_flag) "SHIPMENT APPROVAL STATUS",
(select user_name from fnd_user where user_id=PLLA.last_updated_by) closed_action_by,
-- c.authorization_status,
PLLA.last_update_Date
from
PO_HEADERS_ALL PHA,
PO_LINES_ALL PLA,
PO_LINE_LOCATIONS_ALL PLLA
where 1=1
AND PHA.PO_HEADER_ID = PLA.PO_HEADER_ID
AND PHA.PO_HEADER_ID = PLLA.PO_HEADER_ID
AND PLA.PO_HEADER_ID = PLLA.PO_HEADER_ID
AND PHA.ORG_ID = PLA.ORG_ID
AND PHA.ORG_ID = PLLA.ORG_ID
AND PLA.ORG_ID = PLLA.ORG_ID
AND PLA.PO_LINE_ID = PLLA.PO_LINE_ID
AND PLA.PO_LINE_ID in
(select PO_line_id from apps.rcv_transactions_interface where shipment_num='ES_RT-
63489_20');

5) Clear both the interface tables filtering with the specific ASN number (RCV_headers_interface &
RCV_Transactions_interface) after taking proper back up

Datafix to delete the interface data after taking backup:

** put the shipment numbers as required**


create table M_G702841.BCKRHIINTF04062021

as

select *

from apps.rcv_headers_interface

where shipment_num in ( 'PL_RT-95412_21'

,'ES_RT-77114_21'

,'IT_RT-34271_21'

,'FR_RT040872_21'

,'DE_RT-00139_21'

,'DE_48405_21'

,'ES_RT-75791_21',

'PL_RT-94492_21'

);

create table M_G702841.BCKRTIINTF04062021

as

select *

from apps.rcv_transactions_interface

where shipment_num in ( 'PL_RT-95412_21'

,'ES_RT-77114_21'

,'IT_RT-34271_21'

,'FR_RT040872_21'

,'DE_RT-00139_21'

,'DE_48405_21'

,'ES_RT-75791_21',

'PL_RT-94492_21'

);
--------------------------------------------------------------------------------------------------------------------------------

delete

from apps.rcv_headers_interface

where shipment_num in ( 'PL_RT-95412_21'

,'ES_RT-77114_21'

,'IT_RT-34271_21'

,'FR_RT040872_21'

,'DE_RT-00139_21'

,'DE_48405_21'

,'ES_RT-75791_21',

'PL_RT-94492_21'

);

delete

from apps.rcv_transactions_interface

where shipment_num in ( 'PL_RT-95412_21'

,'ES_RT-77114_21'

,'IT_RT-34271_21'

,'FR_RT040872_21'

,'DE_RT-00139_21'

,'DE_48405_21'

,'ES_RT-75791_21',

'PL_RT-94492_21'

);
commit;

--------------------------------------------------------------------------------------------------------------------------------

6) Change the Technical Succ status to Functional Err status of that ASN in GIS by asking the EAI
team member (i.e Parth Thakore)

7) The last step is, asking business to retrigger the ASN from Human Task (HT)

8) Check the transaction again in RTI table and wait for the Transaction Processor program to pick
it up and process

9) After processing, the ASN data will reflect as Functional Succ in GIS

Happy!!

You might also like