Case 1 (INC2709665) AR-PO flow

Either PO will get created or AP invoice will be created at the Buyer Side.

AP invoice is created or PO is based on the stockable or expense items and accounting needs.

If Invoice is missing we need to identify the source of the invoice first (The supplier).

If it belongs to NA zone we will be able to see it in our ERP (Prod1) or if belongs to third party legacy
system or any other zone such as EUR or ACJ we shall check with that respective team if it has been
successfully created and sent for integration.

We need to identify the document type of invoice and if it is setup in GIS or not. Some of the document
types to receive transactions in GIS

Also we need to identify ship to and bill to location if it is same then the invoice will not be able to
integrate in GIS.

In such cases invoice has to be manually booked by accounting team and will not go in GIS.

Normal AR-PO flow:

AR invoice - GIS- Po interface-po base tables

IG invoices are intragroup invoices which we usually find in GIS Transactions.

Case 2
INC2679071

If the invoices are already booked in Oracle and are not visible in Human Task then we need to
terminate the invoice in GIS.

We can find the status of the invoice in GIS that if the PO or AP invoice are created or not.

If it is functional error then we need to ask EAI team (Integration Team) to terminate the invoice in
GIS.

Reference Incident no: INC2739270

There are generally four states in GIS

Technical Error

Technical success

Functional Error

Functional Success

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

Case 3

INC2955416

When invoices were sent to GIS with wrong bill to location

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

We are creating a Physical receipt therefore it is required to create a PO after creating an AR Invoice

Hence we would have directly created a AP invoice after AR Invoice

As expense items are not stockable so we wont be requiring receipt in such case.
PO would have been created in FOP but we don’t do receiving in oracle directly we do that in a third
party system (eg : BSM). That third party system must have this PO information of Oracle.

If receipt information coming from LS does not have a associated PO then it will fail or if the PO
reference number does not match with the PO number in our system then also receipt is failing

1. If native id has TX it means it belongs to logical stock whose object is PO209A

2. Eg: M21 is Mexico which is going to receive (warehouse)
3. Log id in query output tells us the source, destination and AR invoice.
4. If quantity is received against that PO then we don’t care whether it fails or not
5. If quantity does not gets received then we need to inform micheal Pleakis or Tania Vizcayno in
case of LS
6. For transcodification error we can check with GIS L3 team, P2P team(Syed Khallelulah).

Direct delivery -subinventory is fix

standard receipt – subinventory is not fix

and inspection required

Router process receipt delivery means it will route from receipt creation to delivery

There are two steps receive and delivery for every transaction means two records will be created in
rcv transactions for every PO or item which are receive and delivery

If PO is not present or quantity received is 0 then we need to ask that respective team

Eg : Logical Stock Team (Tirupathama Bodapati, Sameer Allupati)

BSM (Abhilash Mekala)

In LS we receive items through invoice reference number from FOPEUR and then receipt information
will be sent from LS back to FOPAME

Ideal scenario : When shipment reference through FOPEUR will come to LS and receipt will be created
against that shipment reference and in FOPAME PO would be created and approved in advance so
through LS receipt info will be created then in FOPAME and the shipment against which receipt in
getting created in LS should be same shipment against which PO is getting created.

Another scenario when po is not present in FOP although the receipt is created in LS in that case we
need to backtrack and see where it is stuck
Through DECODE the shipto info from FOPEUR and receiving info in FOPAME will be validated

like which inventory or subinventory the item is going to reside.

If PO is not created you can see first in po_headers_interface table by querying invoice number or
shipment reference number found in the native id in attribute1 column to see if it is errored out or
then check E2E or we need to go directly to source to see if AR invoice has been created or not.

If it is created we need to see if any setup is missing or functional error then we will rectify it and get
repush it from GIS again.

We will manually receive the PO then because at first place we were not able to find it in FOP

If Po is not created only then we will go to source, FOPEUR in our case to see if AR invoice is created or
not if we can not see any error in GIS or anywhere else.

In some cases for cross border invoices as the container is manually created from that system and
received in the our system we are unable to find po against those shipments
usually for cross border invoices like MXA, BR,CA and US
 INVOICES MISSING IN GIS

INC2797123 (Invoices Missing in GIS)

Some Possible cases : invalid document type, invoice not sent from the source, same ship to and bill to

And in some cases when

it was not picked by the AR document transfers program then we need to talk to the AR team and get
it retriggered or if it stuck in ar_document_transfers program then we need to see the error and take
action accordingly.

In such cases manual adjustment will be created by the business or a manual PO will be created for
this AR invoice as it was not automatically integrated.

IG invoice related any information - Gabriela Martinez

IG PO related- Ashley Gardener

SDS – Rocio Lara

select
phi.document_num,phi.attribute1,phi.attribute2,phi.attribute5,phi.ship_to_location,phi.approval_statu
s,phi.process_code,
phi.action,phi.creation_date,pie.creation_date,pie.error_message,pie.column_name
from
apps.po_headers_interface phi,
APPS.po_interface_errors pie
where
1=1
and phi.interface_source_code='GIS'
and phi.creation_date like '%DEC-20%'
and phi.process_code='REJECTED'
and phi.interface_header_id=pie.interface_header_id;

If the transaction is between US , Canada or Mexico then shipment number is only the invoice
number. We can find it through waybill number column in ra_customer_trx_all table.

In case of doubt over PO creation kindly communicate Tania or Micheal Pleakis.

If automatic reception of quantity or quantity received is 0 is failed kindly provide the PO’s to tania for
manual reception of PO’s because they got approved late and LS automatic receipts got failed
ASN’S got stuck in Technical Success Status in GIS

Reference Incident :

INC2817037, INC2886278
In this case we need to check shipment in GIS and then we need to check if shipments against those
PO’s are in received status or if stuck somewhere and have to take action accordingly