White Paper Subledger Accounting For Intercompany Transaction Flows V5.6

White Paper
Sub-Ledger Accounting Setups for

Intercompany Transaction Flows
Author: Wayne Greene

Creation Date: Feb 5, 2011
Last Update: July 13, 2012
Contributors
And
Reviewers: Shixin (Jason) Zhang
Rixin Zhu
Application Accounting Definition 118861
File Ref: 386589801.docx
Company Confidential - For internal use only


Contents Define
Overview...................................................................................................................................4
Internal Drop Ship – without modified SLA........................................................................5
Internal Drop Ship – with modified SLA..............................................................................6
Application Accounting Definition.......................................................................................7
PL/SQL Functions...................................................................................................................8
Sub-Ledger Accounting Setups..............................................................................................9
Custom Sources......................................................................................................................10
Assign Custom Sources to Event Class...............................................................................12
XLA Lookups..........................................................................................................................13
Accounting Definition Rules................................................................................................14
Logical Intercompany Event Class......................................................................................15
Logical Intercompany Event Class – Journal Line Definitions........................................16
Sales Order Issue Event Class..............................................................................................18
Sales Order Issue – Deferred COGS Journal Line Types..................................................19
Sales Order Issue – COGS Journal Line Types..................................................................22
Sales Order Issue – Inventory Valuation Journal Line Types..........................................24

PL/SQL Function - XYZ_SALE_INTERCO_FLAG...........................................................26
PL/SQL Function - XYZ_COGS_RECOG_INTERCO_FLAG.........................................29
PL/SQL Function - XYZ_INTERNAL_DROP_RECEIPT.................................................32
PL/SQL Function - XYZ_INTRNL_DROP_RCPT_MRKP...............................................36
PL/SQL Function - XYZ_INTERCO_SEGMENT..............................................................39
PL/SQL Function - XYZ_INTRNL_DROP_COGS_AMT................................................42
PL/SQL Function - XYZ_INTRNL_DROP_INV_AMT....................................................46

Overview
This white paper describes how to modify sub-ledger accounting (SLA) for intercompany transactions when tracking of a separate intercompany markup
dollar amount is required for internal drop ships across international boundaries. This is often a requirement for tax purposes. The current costing system does not
provide for a separation of this markup. Having the markup as a separate accounting entry, instead of added into inventory, allows for accurate end of month
intercompany eliminations.
An internal drop ship is where an internal legal entity in one country takes a sales order from a customer, but then sources the shipment from an internal
warehouse in a different country. This internal warehouse belongs to a different internal legal entity. The warehouse then ships directly to the customer across
international boundaries. The country where the shipment comes from must collect taxes on that transaction based on the profit margin. The profit margin must
be an unbiased arms-length amount. The markup percent is stored in advanced pricing. The markup amount will appear in the receiving legal entity as part of the
Logical Intercompany Shipment Receipt transaction type.
This paper does not address the advanced pricing setup or intercompany transactions flows. These setups are also required. It only addresses the SLA setup.
Each setup below has a description column to further explain the usage and outcome of each setting. These settings have been successfully used in a standard
costing production environment. They are currently being tested in an average costing environment with production go live scheduled for next year. The SLA
settings do not address internal intercompany drop ship RMA. That is an ongoing development.
Sub-ledger Accounting allows customers to modify the accounting entries just before they are transferred to the general ledger.

Internal Drop Ship – without modified SLA
The accounting depicted below is the seeded accounting output for an internal drop ship without any SLA changes.
Transaction Type Description Account DR CR
Logical Intercompany Sales Issue Shipper – at shipper standard cost Inventory - Finished Goods 973.58
Logical Intercompany Sales Issue Shipper – at shipper standard cost Cost of sales - Intercompany 973.58
Logical Intercompany Shipment Receiver – at shipper standard cost plus 1246.21

Receipt
973.58 X .27% markup = 262.86 X currency
conversion rate of 1.0079 = 1246.21 Inventory - Finished Goods
Logical Intercompany Shipment Receiver 1246.2

Receipt Inventory Accrual - Intercompany 1
Logical Sales Order Issue Receiver – when sell to 3rd party customer 1246.2
Inventory - Finished Goods 1
Logical Sales Order Issue Receiver – when sell to 3rd party customer Inventory - Deferred COGS 1246.21

COGS Recognition COGS recognized when revenue is 1246.2
earned Inventory - Deferred COGS 1

earned Cost of Goods Sold – third party

Internal Drop Ship – with modified SLA
The accounting depicted below is the accounting output for an internal drop ship after these SLA changes have been made.
Transaction Type Description Account DR CR
Logical Intercompany Sales Issue Shipper – at shipper standard cost Inventory - Finished Goods 973.58
Logical Intercompany Sales Issue Shipper – at shipper standard cost 973.5

Cost of sales - Intercompany 8
Logical Intercompany Shipment Receiver – 973.58 X currency 981.2

Receipt 7
onversion rate of 1.0079 = 981.27 Inventory - Finished Goods
Logical Intercompany Shipment Receiver – at shipper standard cost plus 264.9

Receipt 4
973.58 X .27% markup = 262.86 X currency
Intercompany Markup -
conversion rate of 1.0079 = 264.94 capitalized
Logical Intercompany Shipment 1246.2

Receipt Inventory Accrual - Interco 1
Logical Sales Order Issue Receiver – when sell to 3rd party customer Inventory - Finished Goods 981.27

Logical Sales Order Issue Receiver – when sell to 3rd party customer 981.2
Inventory - Deferred COGS 7

earned Inventory - Deferred COGS

earned Cost of Goods Sold – third party 7
As can be seen from the example above, the shipping cost is multiplied by a markup of 27%. 973.58 X .27 = 262.86
Then a currency conversion rate of 1.0079 from shipping to receiving company is used to calculate the receiving markup entry. 262.86 X 1.0079 = 264.94
The inventory entry uses the shipping cost multiplied by the currency conversion rate. 973.58 X 1.0079 = 981.27
The receiving standard cost is not used because inventory does not physically enter the receiving warehouse.
The receipt is virtual and used only to calculate third party COGS to be used to calculate profit from revenue on the customer facing transaction.


Application Accounting Definition
Use this next form to create a new Application Accounting Definition.
Cost Manager – SLA -> SLA -> Accounting Setup > Accounting Methods Builder -> Methods and Definitions -> Application Accounting Definitions
First find the old “COST MANAGEMENT” definition. Then use the copy button and modify as listed below.
Definition Chart of Chart of

Definition Description Accounts Accounts
Name
Transaction Accounting
Code
XYZ Cost Manager XYZ Cost Manager XYZ custom Cost XYZ Corp XYZ Corp
Management Accounting Accounting
Flexfield Flexfield

This step may have already been done by another track up until the last step:
Use this next form to tie the newly created Application Accounting Definition to Cost Management.
Cost Manager – SLA -> SLA -> Accounting Setup > Accounting Methods Builder -> Methods and Definitions -> Subledger Accounting Methods
First find the old Oracle “STANDARD_ACCRUAL” definition.
Then use the copy button and modify as listed below.
Method Code = XYZ_STANDARD_ACCRUAL
Method Name = XYZ STANDARD ACCRUAL
Description = XYZ STANDARD ACCRUAL
Chart of Accounts Transaction = XYZ_CORP_ACCOUNTING_FLEXFIELD
Chart of Accounts Accounting = XYZ_CORP_ACCOUNTING_FLEXFIELD
Now modify a single row:
Application = Cost Management
Name = XYZ Cost Management

PL/SQL Functions
PL/SQl functions defined for internal drop ship transactions.
Compile the following PL/SQL functions:
XYZ_SALE_INTERCO_FLAG_V1.txt
XYZ_COGS_RECOG_INTERCO_FLAG_V1.txt
XYZ_INTERNAL_DROP_RECEIPT_V1.txt
XYZ_INTRNL_DROP_RCPT_MRKP_V1.txt
XYZ_INTERCO_SEGMENT_V1.txt
XYZ_INTRNL_DROP_COGS_AMT
XYZ_INTRNL_DROP_INV_AMT
Also, be sure to run the grant and synonym scripts.
Also, be sure to run the create index script for queries.

The actual code for these functions is listed at the end of the paper.

Sub-Ledger Accounting Setups
The SLA seeded definitions may need to be loaded using the concurrent program “Import Application Accounting Definition”.
Context=default
Source File=/pbtlyi/applmgr/1200/bom/12.0.0/patch/115/import/US /cstxlaaad.ldt
Merge Analysis=No
Import Option = Merge
Validate=Yes
To verify the load:
1. Event Model Form

2. Entity = “Material Account Events”
3. Event Class Code = “LOG_INTERCOMPANY”
4. Event Type Codes should be listed

Custom Sources
Now create custom sources using the following form:
Cost Manager – SLA -> SLA -> Accounting Setup > Accounting Methods Builder -> Sources -> Custom Sources
Description Custom Custom PL/SQL Data Segment Accounti Parameter Parameter

ng
Source Source Function Type
Flexfield
Code Name Name
USED IN
SALES
ISSUE
EVENT
Returns “Y” if transaction is internal drop ship XYZ_SALE XYZ_SALE XYZ_SALE Alpha No Inventory Item in TRANSACTION_ID
_INTERCO _INTERCO _INTERCO numer Costing in Costing
_FLAG _FLAG _FLAG ic
For internal drop ship returns the intercompany segment XYZ XYZ XYZ_INTE Alpha Intercompany Yes Inventory Item in TRANSACTION_ID
INTERCO INTERCO RCO_SEG numer Segment Costing in Costing
SEGMENT SEGMENT MENT ic

ng
Flexfield
Code Name Name
Only called by COGS recognition. Returns “Y” if transaction XYZ_COG XYZ_COG XYZ_COG Alpha No Inventory Item in TRANSACTION_ID
is a COGS recognition on an internal drop ship S_RECOG_ S_RECOG_ S_RECOG_ numer Costing in Costing
INTERCO_ INTERCO_ INTERCO_ ic
FLAG FLAG FLAG
Internal drop COGS amt downstream after markup removed XYZ XYZ XYZ_INTR Nume No Inventory Item in TRANSACTION_ID
INTRNL INTRNL NL_DROP ric Costing in Costing
DROP DROP _
COGS COGS COGS_AM
AMT AMT T
Internal drop INV amt downstream after markup removed XYZ XYZ XYZ_INTR Nume No Inventory Item in TRANSACTION_ID
INTRNL INTRNL NL_DROP ric Costing in Costing
DROP INV DROP INV _
AMT AMT INV_AMT
USED IN
INTERCO
MPANY
EVENT
Internal drop inventory receipt amount XYZ_INTE XYZ_INTE XYZ_INTE Nume No Inventory Item in TRANSACTION_ID
RNAL_DR RNAL_DR RNAL_DR ric Costing in Costing
OP_RECEI OP_RECEI OP_RECEI
PT PT PT

ng
Flexfield
Code Name Name
Internal drop receipt markup XYZ_INTR XYZ_INTR XYZ_INTR Nume No Inventory Item in TRANSACTION_ID
NL_DROP NL_DROP NL_DROP ric Costing in Costing
_RCPT_MR _RCPT_MR _RCPT_MR
KP KP KP

Assign Custom Sources to Event Class
Use this next form to assign the custom sources to the “Logical Intercompany” event class.
Cost Manager – SLA -> SLA -> Accounting Setup > Accounting Methods Builder -> Sources -> Accounting Attribute Assignments
Query the event class “Logical Intercompany”.
Create a new row for each entry in the table below.
This will allow the source to be chosen while inside the line type form.
Accounti Source
ng
Attribute
Accounted XYZ_INTERNAL_DROP_RECEIPT
Amount
Entered XYZ_INTRNL_DROP_RCPT_MRK
P
Amount
Accounted XYZ_INTRNL_DROP_RCPT_MRK
P
Amount

Accounti Source
ng
Attribute
Use this next form to assign the custom sources to the “Sales Order Issue” event class.
Cost Manager – SLA -> SLA -> Accounting Setup > Accounting Methods Builder -> Sources -> Accounting Attribute Assignments
Query the event class “Sales Order Issue”.
Create a new row for each entry in the table below.
This will allow the source to be chosen while inside the line type form.
Accounti Source
ng
Attribute
Accounted XYZ INTRNL DROP COGS
AMT
Amount
Accounted XYZ INTRNL DROP INV AMT
Amount


XLA Lookups
Use this next form to create a new XLA Lookup.
Application Developer -> Application -> Lookups -> XLA Lookups
Query type of “XLA_ACCOUNTING_CLASS”
This lookup will appear on the SLA accounting form for each IC markup accounting line..
Code Meaning Description

IC_Marku Inter-company Inter-company
p Markup Markup

Accounting Definition Rules
Use this next form to create an accounting derivation rule for markup account.
Cost Manager – SLA -> SLA -> Accounting Setup > Accounting Methods Builder -> Journal Entry Setups -> Account Derivation Rules
Choose to create new rules as listed below:
Description Rule Rule Chart of Chart of Output Segment Prio Value Value Conditio
rity n
Code Name Accounts Accounts Type Name Type
Transaction Accounti
ng
Inter-company Markup Account. XYZ XYZ INTERCO XYZ_CORP_ACCO XYZ_CORP Segment Account 10 Constant 122500
INTERCO MARKUP UNTING_FLEXFIEL _ACCOUN
MARKUP D TING_FLE
XFIELD
XYZ INTERCO SEGMENT used for XYZ INTERCO XYZ INTERCO XYZ_CORP_ACCO XYZ_CORP Segment Intercompany 10 Source XYZ
intercompany eliminations. SEGMENT SEGMENT UNTING_FLEXFIEL _ACCOUN INTERCO
D TING_FLE SEGMENT
XFIELD

Logical Intercompany Event Class
Go back to the Application Accounting Definition form.
Cost Manager – SLA -> SLA -> Accounting Setup > Accounting Methods Builder -> Methods and Definitions -> Application Accounting Definitions
Query the event class of “Logical Intercompany”.
Then, click on the “Journal Line Definition” button.
Click the “Copy Definition” button.
Definition Code = XYZ_LOGIC_INTERCO
Definition Name = XYZ Logical Intercompany
Description = XYZ Logical Intercompany
After the new Journal Line Definition has been created, go back to the Application Accounting Definition form.
Query the event class of “Logical Intercompany”.
Delete the old journal line definition that is attached at the bottom of the form and add the new one that was just created.

Logical Intercompany Event Class – Journal Line Definitions
Once you have defined the new Journal Line Definition, then execute the following steps:
Select the journal line type of “Inventory Valuation”.
Disable this type.
Click the line type button.
Click the “Copy” button.
Create new line types as described above by using the data below.
Repeat once for each row in the table below:

Description Line Transaction Accounting Rounding Condition Accounting
Event Class Name
Type Chart of Class Class Attribute
Code Accounts Assignments
:
Source for
Accounted
Amount
Sales Issue at std cost. Logical XYZ INTRNL XYZ XYZ_CORP_A Inventory Inventory Accounting Line Type =1 Accounted
Intercompany CCOUNTING_ Valuation Valuation AND
DROP ISSUE INTRNL Amount
FLEXFIELD
DROP Accounting Event Type
ISSUE =
( WHEN YOU COPY Code =
'LOG_IC_SALES_ISSUE'
THE LINE TYPE, Accounted
MAKE SURE IT Amount
DOES NOT
CHANGE THE
EVENT CLASS. )
Inv receipt markup – executes Logical XYZ_INTRNL_DROP XYZ_INTRNL_ XYZ_CORP_A Inventory Inventory Accounting Line Type =1 Accounted
with the XYZ
INTRNL Intercompany _MRKP DROP_MRKP CCOUNTING_ Valuation Valuation AND
Amount
FLEXFIELD
DROP RCPT INV Accounting Event Type
Name = =
LOG_IC_SHIPMENT_RC XYZ_INTR
PT NL_DROP_
RCPT_MRK
P

Description Line Transaction Accounting Rounding Condition Accounting
Event Class Name
Type Chart of Class Class Attribute
Code Accounts Assignments
:
Source for
Accounted
Amount
Be sure to enter
ADR of XYZ
INTERCO SEGMENT
for the above type on
the intercompany
segment
And
XYZ INTERCO
MARKUP on the
account segment
Inv receipt without markup Logical XYZ INTRNL XYZ XYZ_CORP_A Inventory Inventory Accounting Line Type =1 Accounted
Intercompany CCOUNTING_ Valuation Valuation AND
DROP RCPT INV INTRNL Amount
FLEXFIELD
DROP Accounting Event Type
This includes the PPV amount RCPT INV Name = =
LOG_IC_SHIPMENT_RC
PT XYZ
INTERNAL
Executes with
XYZ_INTRNL_DROP_MRKP
DROP
RECEIPT

On new line types, always turn on debit and switch debit/credit. This means positive will be debit and negative will be credit.
In the Logical Intercompany event class, on the journal line types of XYZ_INTERCO_MARKUP and Intercompany Accrual enter the following:
1. Segment = Intercompany, Rule Name = XYZ INTERCO SEGMENT

Sales Order Issue Event Class
Go back to the Application Accounting Definitions form.
Query the event class of “Sales Order Issue”.
Then, click on the “Journal Line Definition” button.
Click the “Copy Definition” button.
Definition Code = XYZ SALES ORDER ISSUE
Definition Name = XYZ Sales Order Issue
Description = XYZ Sales Order Issue
After the new Journal Line Definition has been created, go back to the Application Accounting Definition form.
Query the event class of “Sales Order Issue”.
Delete the old journal line definition that is attached at the bottom of the form and add the new one that was just created.


Sales Order Issue – Deferred COGS Journal Line Types
Since third party sales and logical sales issue share the same journal line types, if you modify one, you must redefine them all.
Select the journal line type of “Deferred COGS”.
Disable this type.

Description Line Transaction Accounting Rounding Debit Condition Accounting
Event Class Name
Type Chart of Class Class / Attribute
Code Accounts Credit Assignments:
Source for
Accounted
Amount
THIRD PARTY AND Sales Order XYZ COGS XYZ COGS XYZ_CORP_A Deferred Cost Deferred Debit Accounting Line Type Accounted
EXTERNAL DROP Issue CCOUNTING_ of Goods Sold Cost of =36
RECOG RECOG Amount
COGS RECOG FOR FLEXFIELD Goods Sold
DEFERRED 3RD 3RD AND
DEFERRED DEFERRED =
Accounting Event
Type Name = 'COGS Accounted
Recognition' Amount
AND
XYZ COGS RECOG

INTERCO FLAG = 'N'

Event Class Name
Source for
Accounted
Amount
CUSTOMER FACING Sales Order XYZ COGS XYZ COGS XYZ_CORP_A Deferred Cost Deferred Accounting Line Type XYZ INTRNL
INTERNAL DROP COGS Issue CCOUNTING_ of Goods Sold Cost of =36
RECOG RECOG DROP COGS
RECOG FOR DEFERRED FLEXFIELD Goods Sold
COGS DEFERRED DEFERRED AND AMT
Accounting Event
Type Name = 'COGS
Recognition'
CREDIT – THIS IS AND

BECAUSE THE
CUSTOM SOURCE XYZ COGS RECOG
ALWAYS RETURNS A INTERCO FLAG = 'Y'
POSITIVE AMOUNT
AND IS ALSO USED
FOR THE COGS ENTRY,
BUT THIS ENTRY
NEEDS TO BE
CREDITED

Event Class Name
Source for
Accounted
Amount
XYZ COGS RMA Sales Order XYZ COGS XYZ COGS XYZ_CORP_A Deferred Cost Deferred Debit Accounting Line Type Accounted
Issue CCOUNTING_ of Goods Sold Cost of =36
DEFERRED RMA RMA Amount
FLEXFIELD Goods Sold
DEFERRED DEFERRED AND
=
Accounting Event
Type Name = 'RMA Accounted
Receipt'
Amount
AND
XYZ COGS RECOG

INTERCO FLAG = 'N'
THIRD PARTY SHIP Sales Order XYZ XYZ XYZ_CORP_A Deferred Cost Deferred Debit Accounting Line Type Accounted
AND EXTERNAL DROP Issue CCOUNTING_ of Goods Sold Cost of =36 AND Accounting
DEFERRED DEFERRED Amount
SHIP DCOGS FLEXFIELD Goods Sold Event Type Name =
COGS COGS 'Sales Order Issue'
AND
XYZ_SALE_INTERCO
_FLAG = 'N'

Event Class Name
Source for
Accounted
Amount
customer facing logical Sales Order XYZ XYZ XYZ_CORP_A Deferred Cost Deferred Accounting Line Type Accounted
sales issue deferred Issue CCOUNTING_ of Goods Sold Cost of =36
LOGICAL LOGICAL Amount
COGS FLEXFIELD Goods Sold
DEFERRED DEFERRED AND
COGS COGS =
Accounting Event
DEBIT Type Name = 'Logical XYZ_INTRNL_D
Sales Order Issue' ROP_INV_AMT
AND
XYZ SALE INTERCO

FLAG = 'Y'

Sales Order Issue – COGS Journal Line Types
Select the journal line type of “Cost of Goods Sold”.
Disable this type.

Description Line Transaction Accountin Rounding Debit Condition Accounting
Event Name g
Type Chart of Class / Attribute
Class
Class
Code Accounts Credi Assignments
t :
Source for
Accounted
Amount
CUSTOMER FACING Sales Order XYZ COGS XYZ XYZ_CORP_AC Cost of Cost of Debit Accounting Line Type XYZ
INTERNAL DROP COGS Issue COUNTING_FL Goods Sold Goods Sold =35
RECOG COGS INTRNL
RECOG FOR DEFERRED EXFIELD
COGS INTERCO RECOG AND DROP
INTERC COGS AMT
Accounting Event Type
O
Name = 'COGS
Recognition'
AND
XYZ COGS RECOG

INTERCO FLAG = 'Y'
THIRD PARTY AND Sales Order XYZ COGS XYZ XYZ_CORP_AC Cost of Cost of Debit Accounting Line Type Accounted
EXTERNAL DROP COG Issue COUNTING_FL Goods Sold Goods Sold =35
RECOG SO COGS Amount
RECOG COGS AMT EXFIELD
RECOG AND
SO =
Name = 'COGS Accounted
Recognition'
Amount
AND
XYZ COGS RECOG

INTERCO FLAG = 'N'

Description Line Transaction Accountin Rounding Debit Condition Accounting
Event Name g
Type Chart of Class / Attribute
Class
Class
Code Accounts Credi Assignments
t :
Source for
Accounted
Amount
XYZ COGS RMA Sales Order XYZ COGS XYZ XYZ_CORP_AC Cost of Cost of Debit Accounting Line Type Accounted
Issue COUNTING_FL Goods Sold Goods Sold =35
RMA COGS Amount
EXFIELD
RMA AND
=
Name = 'RMA Receipt' Accounted
AND Amount
XYZ COGS RECOG
INTERCO FLAG = 'N'

Sales Order Issue – Inventory Valuation Journal Line Types
Once you have defined the new Journal Line Definition, then execute the following steps:
Select the journal line type of “Inventory Valuation”.
Disable this type.

Event Name
Class
Code Accounts Credit Assignments
:
Source for
Accounted
Amount
internal drop ship Sales XYZ INT XYZ INT XYZ_CORP_AC Inventory Inventory CREDIT – Accounting Line Accounted
Order COUNTING_FL Valuation Valuation BECAUSE THE Type =1 AND
DROP INV DROP INV Amount
Issue EXFIELD CUSTOM SOURCE
VALUATI VALUATI RETURNS A Accounting Event
customer facing logical ON ON POSITIVE AND IS Type Name = =
sales issue inv valuation ALSO USED FOR 'Logical Sales
THE DEFERRED Order Issue' XYZ_INTR
COGS SIDE OF THE NL_DROP_I
LOGICAL SALES AND
NV_AMT
ISSUE BUT HERE
WE NEED A XYZ SALE
CREDIT SINCE INTERCO FLAG
SHIPPING OUT = 'Y'
INVENTORY
RMA Sales XYZ RMA XYZ RMA XYZ_CORP_AC Inventory Inventory Debit Accounting Line Accounted
Order COUNTING_FL Valuation Valuation Type =1 AND
INV INV Amount
Issue EXFIELD
VALUATI VALUATI Accounting Event
ON ON Type Name = =
'RMA Receipt'
AND Accounted
Amount
XYZ SALE
INTERCO FLAG
= 'N'

Event Name
Class
Code Accounts Credit Assignments
:
Source for
Accounted
Amount
3rd party and external Sales XYZ SO XYZ SO XYZ_CORP_AC Inventory Inventory Debit Accounting Line Accounted
drop so inv valuation Order COUNTING_FL Valuation Valuation Type =1 AND
INV INV Amount
Issue EXFIELD
VALUATI VALUATI Accounting Event
ON ON Type Name = =
'Sales Order Issue'
Accounted
AND Amount
XYZ SALE
INTERCO FLAG
= 'N'


PL/SQL Function - XYZ_SALE_INTERCO_FLAG
CREATE OR REPLACE
FUNCTION XYZ_SALE_INTERCO_FLAG
p_Inventory_Item IN NUMBER
, p_transaction_id IN NUMBER
RETURN VARCHAR2
IS
-- **** RETURN Y ON SALES ISSUE TRANSACTIONS IF IT IS INTERCOMPANY
xyz_sale_interco_flag VARCHAR2(1);
BEGIN
xyz_sale_interco_flag:='N';
SELECT

/*+ ORDERED */
'Y'
INTO
xyz_sale_interco_flag
FROM
mtl_material_transactions mmt
, mtl_material_transactions mmt2
, mtl_transaction_types ttype2
WHERE
/*+ ORDERED_PREDICATES */
mmt.transaction_id = p_transaction_id -- **** FROM THE PARENT TRANSACTION OF SALES ISSUE
AND
mmt2.parent_transaction_id = mmt.parent_transaction_id
AND
ttype2.transaction_type_id = mmt2.transaction_type_id
AND
-- **** THIS INSURES WE ARE DEALING WITH ONE OF THE LOGICAL INTERCOMPANY TRANSACTIONS
ttype2.transaction_type_name = 'Logical Intercompany Shipment Receipt'

-- ************************************
FND_FILE.NEW_LINE( FND_FILE.LOG, 1 );
FND_FILE.PUT_LINE( FND_FILE.LOG,
' SALES ISSUE INTERCO FLAG FUNCTION '
);
' TRANSACTION ID: ' || p_transaction_id
);
' ITEM ID: ' || p_inventory_item
);
' SALES ISSUE INTERCO FLAG: ' || xyz_sale_interco_flag
);
-- ************************************
RETURN xyz_sale_interco_flag;
-- ************************************
EXCEPTION

WHEN NO_DATA_FOUND THEN
' SALES ISSUE INTERCO FLAG FUNCTION - NO DATA'
);
);
);
' SALES ISSUE INTERCO FLAG: ' || xyz_sale_interco_flag
);

WHEN OTHERS THEN
' ERROR: ' || SUBSTR(SQLERRM,1,80)
);
' SALES ISSUE INTERCO FLAG FUNCTION '
);
' ERROR TRANSACTION ID: ' || p_transaction_id
);
' ERROR ITEM ID: ' || p_inventory_item
);

END;

PL/SQL Function - XYZ_COGS_RECOG_INTERCO_FLAG
CREATE OR REPLACE
FUNCTION XYZ_COGS_RECOG_INTERCO_FLAG
p_Inventory_Item IN NUMBER
RETURN VARCHAR2
IS
-- **** RETURNS Y IF COGS RECOG IS ON INTERCOMPANY
xyz_cogs_recog_interco_flag VARCHAR2(1);
BEGIN
xyz_cogs_recog_interco_flag:='N';

SELECT
/*+ ORDERED */
'Y'
INTO
xyz_cogs_recog_interco_flag
FROM
WHERE
mmt.transaction_id = p_transaction_id -- **** COGS RECOG TRANSACTION
AND
-- **** THIS WILL PULL IN THE SOURCE TRANS OF COGS RECOG
EXISTS
SELECT
/*+ ORDERED */
mmt2.transaction_id
FROM
mtl_material_transactions mmt2
, inv.mtl_transaction_types ttype

WHERE
mmt2.transaction_source_id = mmt.transaction_source_id
AND
-- **** THERE COULD BE MULTIPLE ITEMS WITH DIFFERENT SOURCES
mmt2.inventory_item_id = mmt.inventory_item_id
AND
ttype.transaction_type_id = mmt2.transaction_type_id
AND
-- **** THIS INSURES WE ARE DEALING WITH AN INTERNAL DROP SHIP
ttype.transaction_type_name = 'Logical Intercompany Shipment Receipt'
-- ************************************
' COGS RECOG INTERCO FLAG FUNCTION '
);

);
);
' COGS RECOG INTERCO FLAG: ' || xyz_cogs_recog_interco_flag
);
-- ************************************
RETURN xyz_cogs_recog_interco_flag;
-- ************************************
EXCEPTION
WHEN NO_DATA_FOUND THEN

' COGS RECOG INTERCO FLAG FUNCTION - NO DATA'
);
);
);
' COGS RECOG INTERCO FLAG: ' || xyz_cogs_recog_interco_flag
);
WHEN OTHERS THEN

);
' COGS RECOG INTERCO FLAG FUNCTION '
);
);
);
END;

PL/SQL Function - XYZ_INTERNAL_DROP_RECEIPT
CREATE OR REPLACE
FUNCTION XYZ_INTERNAL_DROP_RECEIPT -- **** INTERNAL DROP SHIP LOGICAL RECEIPT
p_inventory_Item IN NUMBER
RETURN NUMBER
IS
xyz_no_markup_inv_cost NUMBER;
BEGIN
xyz_no_markup_inv_cost := 0;
SELECT
/*+ ORDERED */

ROUND (
( mmt3.intercompany_cost
( mmt3.intercompany_cost - ( rates.conversion_rate * mmt1.actual_cost ) )
* mmt3.transaction_quantity
,2
) extend_inv
INTO
xyz_no_markup_inv_cost
FROM

, gl_daily_rates rates
WHERE
mmt.transaction_id = p_transaction_id
-- *********************************************
AND
AND
AND
ttype1.transaction_type_name = 'Sales order issue'
-- *********************************************
AND
AND
AND
ttype2.transaction_type_name = 'Logical Intercompany Sales Issue'
-- ***************************************************
AND

AND
AND
-- *********************************************
-- **** WE NEED TO CONVERT THE SHIP AMT TO THE RECEIPT CURRENCY
AND
rates.from_currency = mmt2.currency_code
AND
rates.to_currency = mmt3.currency_code
AND
rates.conversion_date = TRUNC (mmt.transaction_date)
AND
--rates.conversion_type = '1001' -- **** get from profile???
rates.conversion_type = 'Corporate' -- **** get from profile???
-- ************************************

' XYZ_INTERNAL_DROP_RECEIPT '
);
);
);
' xyz_no_markup_inv_cost: ' || xyz_no_markup_inv_cost
);
-- ************************************
RETURN xyz_no_markup_inv_cost;
-- ************************************
EXCEPTION
WHEN OTHERS THEN


);
' XYZ_INTERNAL_DROP_RECEIPT '
);
);
);

END;


PL/SQL Function - XYZ_INTRNL_DROP_RCPT_MRKP
CREATE OR REPLACE
FUNCTION XYZ_INTRNL_DROP_RCPT_MRKP -- **** INTERNAL DROP SHIP LOGICAL RECEIPT MARKUP
RETURN NUMBER
IS
xyz_markup_inv_cost NUMBER;
BEGIN
xyz_markup_inv_cost := 0;
SELECT
/*+ ORDERED */

ROUND (
( mmt2.actual_cost * mmt2.transaction_quantity )
,2
---- **** MUST ROUND SEPERATELY FROM SUBTRACT SO ENTRIES BALANCE WITHOUT ROUNDING ERROR
ROUND (
( mmt3.actual_cost *
( mmt2.actual_cost / mmt2.intercompany_cost )
,2
) markup
INTO
xyz_markup_inv_cost
FROM

, inv.mtl_transaction_types ttype
, inv.mtl_transaction_types ttype2
WHERE
AND
AND
ttype.transaction_type_id(+) = mmt2.transaction_type_id
AND
AND
AND
ttype2.transaction_type_id(+) = mmt3.transaction_type_id
AND

-- ************************************
' XYZ_INTRNL_DROP_RCPT MARKUP '
);
);
);
' xyz_markup_inv_cost: ' || xyz_markup_inv_cost
);
-- ************************************
RETURN xyz_markup_inv_cost;
-- ************************************
EXCEPTION

WHEN OTHERS THEN
);
' XYZ_INTRNL_DROP_RCPT MARKUP '
);
);
);
xyz_markup_inv_cost := 0;

RETURN xyz_markup_inv_cost;
END;

PL/SQL Function - XYZ_INTERCO_SEGMENT
CREATE OR REPLACE
FUNCTION XYZ_INTERCO_SEGMENT
RETURN VARCHAR2
IS
xyz_interco_segment VARCHAR2(3);
BEGIN
xyz_interco_segment:='000';
SELECT

/*+ ORDERED */
comb.segment1
INTO
xyz_interco_segment
FROM
, mtl_transaction_types ttype
, gl_code_combinations comb
WHERE
-- **** INTERNAL DROP SHIP INTERCOMPANY TRANS
AND
ttype.transaction_type_id = mmt.transaction_type_id
AND
AND

AND
AND
-- ****
AND
comb.code_combination_id = mmt2.distribution_account_id;
-- ************************************
' INTERCO SEGMENT FUNCTION '
);
);
' ITEM ID: ' || p_inventory_Item
);

' INTERCO SEGMENT: ' || xyz_interco_segment
);
-- ************************************
RETURN xyz_interco_segment;
-- ************************************
EXCEPTION
WHEN OTHERS THEN
);
' INTERCO SEGMENT FUNCTION '
);


);
' ERROR ITEM ID: ' || p_inventory_Item
);
xyz_interco_segment:='000';
RETURN xyz_interco_segment;
END;


PL/SQL Function - XYZ_INTRNL_DROP_COGS_AMT
CREATE OR REPLACE
FUNCTION XYZ_INTRNL_DROP_COGS_AMT -- **** INV RCPT NO MARKUP ON INTERNAL DROP SHIP
RETURN NUMBER
IS
BEGIN
-- **** THIS IS USED BY INTERNAL DROP SHIPS TO ADJUST THE
-- **** CUSTOMER FACING SIDE OF THE TRANSACTION

SELECT
/*+ ORDERED */
ROUND (
,2
) extend_inv
INTO
FROM

WHERE
mmt.transaction_id = p_transaction_id -- **** COGS RECOG
AND
-- **** THIS WILL PULL IN THE SOURCE TRANS OF COGS RECOG
mmt1.transaction_source_id = mmt.transaction_source_id
AND
-- **** THERE COULD BE MULTIPLE ITEMS PER ORDER
mmt1.inventory_item_id = mmt.inventory_item_id
AND
AND
-- *********************************************
AND

mmt2.parent_transaction_id = mmt1.parent_transaction_id
AND
AND
-- ***************************************************
AND
mmt3.parent_transaction_id = mmt1.parent_transaction_id
AND
AND
-- *********************************************
AND
AND
AND


AND
-- ************************************
' XYZ_INTRNL_DROP_COGS_AMT '
);
);
);
);

-- ************************************
-- ************************************
EXCEPTION
WHEN OTHERS THEN
);
' XYZ_INTRNL_DROP_COGS_AMT '
);
);


);
END;


PL/SQL Function - XYZ_INTRNL_DROP_INV_AMT
CREATE OR REPLACE
FUNCTION XYZ_INTRNL_DROP_INV_AMT -- **** INV RCPT NO MARKUP ON INTERNAL DROP SHIP
(
)
RETURN NUMBER
IS
BEGIN
-- **** THIS IS USED BY INTERNAL DROP SHIPS TO ADJUST THE

-- **** CUSTOMER FACING SIDE OF THE TRANSACTION
SELECT
/*+ ORDERED */

ROUND (
(
-
)
)
,2
) extend_inv
INTO
FROM
WHERE

-- *********************************************
AND
AND
AND
-- *********************************************
AND
AND
AND
-- ***************************************************
AND
AND
AND
-- *********************************************

AND
AND
AND
AND
;
-- ************************************
' XYZ_INTRNL_DROP_INV_AMT '
);
);
);

);
-- ************************************
-- ************************************
EXCEPTION
WHEN OTHERS THEN
);
' XYZ_INTRNL_DROP_INV_AMT '
);
);

);
END;

White Paper Subledger Accounting For Intercompany Transaction Flows V5.6

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

White Paper Subledger Accounting For Intercompany Transaction Flows V5.6

Încărcat de

Drepturi de autor:

Formate disponibile

White Paper

Sub-Ledger Accounting Setups for

Author: Wayne Greene

Application Accounting Definition 118861

File Ref: 386589801.docx

Company Confidential - For internal use only

File Ref: 386589801.docx

Company Confidential - For internal use only

File Ref: 386589801.docx

Company Confidential - For internal use only

Application Accounting Definition 148864

File Ref: 386589801.docx

Company Confidential - For internal use only

Application Accounting Definition 158865

File Ref: 386589801.docx

Company Confidential - For internal use only

Transaction Type Description Account DR CR

Logical Intercompany Shipment Receiver – at shipper standard cost plus 1246.21

conversion rate of 1.0079 = 1246.21 Inventory - Finished Goods

Logical Intercompany Shipment Receiver 1246.2

Application Accounting Definition 168866

File Ref: 386589801.docx

Company Confidential - For internal use only

COGS Recognition COGS recognized when revenue is 1246.21

Application Accounting Definition 178867

File Ref: 386589801.docx

Company Confidential - For internal use only

Transaction Type Description Account DR CR

Logical Intercompany Sales Issue Shipper – at shipper standard cost 973.5

Logical Intercompany Shipment Receiver – 973.58 X currency 981.2

Logical Intercompany Shipment Receiver – at shipper standard cost plus 264.9

Logical Intercompany Shipment 1246.2

Application Accounting Definition 188868

File Ref: 386589801.docx

Company Confidential - For internal use only

COGS Recognition COGS recognized when revenue is 981.27

COGS Recognition COGS recognized when revenue is 981.2

Application Accounting Definition 198869

File Ref: 386589801.docx

Company Confidential - For internal use only

File Ref: 386589801.docx

Company Confidential - For internal use only

Use this next form to create a new Application Accounting Definition.

Definition Chart of Chart of

Application Accounting Definition 11188611

File Ref: 386589801.docx

Company Confidential - For internal use only

First find the old Oracle “STANDARD_ACCRUAL” definition.

Then use the copy button and modify as listed below.

Method Code = XYZ_STANDARD_ACCRUAL

Method Name = XYZ STANDARD ACCRUAL

Description = XYZ STANDARD ACCRUAL

Chart of Accounts Transaction = XYZ_CORP_ACCOUNTING_FLEXFIELD

Chart of Accounts Accounting = XYZ_CORP_ACCOUNTING_FLEXFIELD

Now modify a single row:

Application = Cost Management

Name = XYZ Cost Management

Application Accounting Definition 11288612

File Ref: 386589801.docx

Company Confidential - For internal use only

Compile the following PL/SQL functions:

Also, be sure to run the grant and synonym scripts.

Also, be sure to run the create index script for queries.