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

Reviewers: Shixin (Jason) Zhang

Rixin Zhu

File Ref: document.docx

Company Confidential - For internal use only

Application Accounting Definition 119561

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 Receipt Receiver – at shipper standard cost plus

973.58 X .27% markup = 262.86 X currency

conversion rate of 1.0079 = 1246.21 Inventory - Finished Goods

1246.21

Logical Intercompany Shipment Receipt Receiver Inventory Accrual - Intercompany 1246.21

Logical Sales Order Issue Receiver – when sell to 3rd party customer Inventory - Finished Goods 1246.21

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

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

1246.21

COGS Recognition COGS recognized when revenue is earned Cost of Goods Sold – third party

1246.21

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 Cost of sales - Intercompany 973.58

Logical Intercompany Shipment Receipt Receiver – 973.58 X currency

onversion rate of 1.0079 = 981.27 Inventory - Finished Goods

981.27

Logical Intercompany Shipment Receipt Receiver – at shipper standard cost plus

973.58 X .27% markup = 262.86 X currency

conversion rate of 1.0079 = 264.94 Intercompany Markup - capitalized

264.94

Logical Intercompany Shipment Receipt Inventory Accrual - Interco 1246.21

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 Inventory - Deferred COGS 981.27

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

981.27

COGS Recognition COGS recognized when revenue is earned Cost of Goods Sold – third party

981.27

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

NameDescription

Chart of Accounts Transaction

Chart of Accounts Accounting

XYZ Cost Manager

XYZ custom Cost Management

XYZ Corp Accounting 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 Form2. 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

Source

Custom

Source

PL/SQL

Function

Segment Accounting

Flexfield

Parameter Parameter

USED IN SALES ISSUE EVENT

Returns “Y” if transaction is internal drop ship XYZ_SALE_INTERCO_FLAG

XYZ_SALE_INTERCO_FLAG

Alphanumeric

No Inventory Item in Costing

TRANSACTION_ID in Costing

For internal drop ship returns the intercompany segment

XYZ INTERCO SEGMENT

XYZ_INTERCO_SEGMENT

Alphanumeric

Intercompany Segment

Yes Inventory Item in Costing

Description Custom

Source

Custom

Source

PL/SQL

Function

Segment Accounting

Flexfield

Parameter Parameter

Only called by COGS recognition. Returns “Y” if transaction is a COGS recognition on an internal drop ship

XYZ_COGS_RECOG_INTERCO_FLAG

Alphanumeric

Internal drop COGS amt downstream after markup removed

XYZ INTRNL DROP COGS AMT

XYZ_INTRNL_DROP_ COGS_AMT

Numeric

Internal drop INV amt downstream after markup removed

XYZ INTRNL DROP INV AMT

XYZ_INTRNL_DROP_ INV_AMT

Numeric

USED IN INTERCOMPANY EVENT

Internal drop inventory receipt amount XYZ_INTERNAL_DROP_RECEIPT

XYZ_INTERNAL_DROP_RECEIPT

Numeric

Description Custom

Source

Custom

Source

PL/SQL

Function

Segment Accounting

Flexfield

Parameter Parameter

Internal drop receipt markup XYZ_INTRNL_DROP_RCPT_MRKP

XYZ_INTRNL_DROP_RCPT_MRKP

Numeric

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.

Accounting

Attribute

Source

Accounted

Amount

XYZ_INTERNAL_DROP_RECEIPT

Entered

Amount

Accounted

Amount

Accounting

Attribute

Source

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.

Accounting

Attribute

Source

Accounted

Amount

Accounting

Attribute

Source

Accounted

Amount

XYZ INTRNL DROP INV AMT

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_Markup

Inter-company 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

Chart of

Accounts

Transaction

Chart of

Accounts

Accounting

Output

Segment

Priority

Value Condition

Inter-company Markup Account. XYZ INTERCO MARKUP

XYZ INTERCO MARKUP

XYZ_CORP_ACCOUNTING_FLEXFIELD

Segment

Account 10 Constant

122500

XYZ INTERCO SEGMENT used for intercompany eliminations.

XYZ INTERCO SEGMENT

Segment

Intercompany

10 Source XYZ INTERCO SEGMENT

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:

DescriptionEvent Class

NameTransaction

Chart of

Accounts

Accounting

Rounding

Condition Accounting

Attribute

Assignments:

Source for Accounted Amount

Sales Issue at std cost.

( WHEN YOU COPY THE LINE TYPE, MAKE SURE IT DOES NOT CHANGE THE EVENT CLASS. )

Logical Intercompany

XYZ INTRNL DROP ISSUE

Inventory Valuation

Accounting Line Type =1 AND

Accounting Event Type Code = 'LOG_IC_SALES_ISSUE'

Accounted Amount

Inv receipt markup –

executes with the XYZ INTRNL DROP RCPT INV

XYZ_INTRNL_DROP_MRKP

Inventory Valuation

Accounting Event Type Name =

LOG_IC_SHIPMENT_RCPT

Accounted Amount

NameTransaction

Chart of

Accounts

Accounting

Rounding

Attribute

Assignments:

Be sure to enter ADR of XYZ INTERCO SEGMENT for the above type on the intercompany segment

XYZ INTERCO MARKUP on the account segment

Inv receipt without markup

This includes the PPV amount

Executes with XYZ_INTRNL_DROP_MRKP

XYZ INTRNL DROP RCPT INV

Inventory Valuation

Accounting Event Type Name = LOG_IC_SHIPMENT_RCPT

Accounted Amount

XYZ INTERNAL 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.

NameTransaction

Chart of

Accounts

Accounting

Rounding

Credit

Attribute

Assignments:

THIRD PARTY AND EXTERNAL DROP COGS RECOG FOR DEFERRED

Sales Order Issue

XYZ COGS RECOG 3RD DEFERRED

Deferred Cost of Goods Sold

Debit Accounting Line Type =36

Accounting Event Type Name = 'COGS Recognition'

XYZ COGS RECOG INTERCO FLAG = 'N'

Accounted Amount

NameTransaction

Chart of

Accounts

Accounting

Rounding

Credit

Attribute

Assignments:

CUSTOMER FACING INTERNAL DROP COGS RECOG FOR DEFERRED COGS

CREDIT – THIS IS BECAUSE THE CUSTOM SOURCE ALWAYS RETURNS A POSITIVE AMOUNT AND IS ALSO USED FOR THE COGS ENTRY, BUT THIS ENTRY NEEDS TO BE CREDITED

Sales Order Issue

XYZ COGS RECOG DEFERRED

Accounting Line Type =36

XYZ COGS RECOG INTERCO FLAG = 'Y'

NameTransaction

Chart of

Accounts

Accounting

Rounding

Credit

Attribute

Assignments:

XYZ COGS RMA DEFERRED

Sales Order Issue

XYZ COGS RMA DEFERRED

Accounting Event Type Name = 'RMA Receipt'

Accounted Amount

Accounted

Amount

THIRD PARTY SHIP AND EXTERNAL DROP SHIP DCOGS

Sales Order Issue

XYZ DEFERRED COGS

Debit Accounting Line Type =36 AND Accounting Event Type Name = 'Sales Order Issue' AND XYZ_SALE_INTERCO_FLAG = 'N'

Accounted Amount

NameTransaction

Chart of

Accounts

Accounting

Rounding

Credit

Attribute

Assignments:

customer facing logical sales issue deferred COGS

Sales Order Issue

XYZ LOGICAL DEFERRED COGS

Accounting Line Type =36

Accounting Event Type Name = 'Logical Sales Order Issue'

XYZ SALE INTERCO FLAG = 'Y'

Accounted Amount

Sales Order Issue – COGS Journal Line Types

Select the journal line type of “Cost of Goods Sold”.

Disable this type.

NameTransaction

Chart of

Accounts

Accounting

Rounding

Credit

Attribute

Assignments:

CUSTOMER FACING INTERNAL DROP COGS RECOG FOR DEFERRED COGS

Sales Order Issue

XYZ COGS RECOG INTERCO

Cost of Goods Sold

XYZ COGS RECOG INTERCO FLAG = 'Y'

THIRD PARTY AND EXTERNAL DROP COG RECOG COGS AMT

Sales Order Issue

XYZ COGS RECOG SO

Cost of Goods Sold

Accounted Amount

Accounted

Amount

NameTransaction

Chart of

Accounts

Accounting

Rounding

Credit

Attribute

Assignments:

XYZ COGS RMA Sales Order Issue

XYZ COGS RMA

Cost of Goods Sold

Accounting Event Type Name = 'RMA Receipt'

Accounted Amount

Accounted

Amount

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.

NameTransaction

Chart of

Accounts

Accounting

Rounding

Credit

Attribute

Assignments:

internal drop ship

customer facing logical sales issue inv valuation

Sales Order Issue

XYZ INT DROP INV VALUATION

Inventory Valuation

CREDIT – BECAUSE THE CUSTOM SOURCE RETURNS A POSITIVE AND IS ALSO USED FOR THE DEFERRED COGS SIDE OF THE LOGICAL SALES ISSUE BUT HERE WE NEED A CREDIT SINCE SHIPPING OUT INVENTORY

Accounting Event Type Name = 'Logical Sales Order Issue'

XYZ SALE INTERCO FLAG = 'Y'

Accounted Amount

RMA Sales Order Issue

XYZ RMA INV VALUATION

Inventory Valuation

Debit Accounting Line Type =1 AND

Accounting Event Type Name = 'RMA Receipt' AND

XYZ SALE INTERCO FLAG = 'N'

Accounted Amount

NameTransaction

Chart of

Accounts

Accounting

Rounding

Credit

Attribute

Assignments:

3rd party and external drop so inv valuation

Sales Order Issue

XYZ SO INV VALUATION

Inventory Valuation

Debit Accounting Line Type =1 AND

Accounting Event Type Name = 'Sales Order Issue'

XYZ SALE INTERCO FLAG = 'N'

Accounted Amount

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

-- **** RETURN Y ON SALES ISSUE TRANSACTIONS IF IT IS INTERCOMPANY

xyz_sale_interco_flag VARCHAR2(1);

xyz_sale_interco_flag:='N';

SELECT

/*+ ORDERED */

xyz_sale_interco_flag

mtl_material_transactions mmt

, mtl_material_transactions mmt2

, mtl_transaction_types ttype2

/*+ ORDERED_PREDICATES */

mmt.transaction_id = p_transaction_id -- **** FROM THE PARENT TRANSACTION OF SALES ISSUE

mmt2.parent_transaction_id = mmt.parent_transaction_id

ttype2.transaction_type_id = mmt2.transaction_type_id

-- **** 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

PL/SQL Function - XYZ_COGS_RECOG_INTERCO_FLAG

CREATE OR REPLACE

FUNCTION XYZ_COGS_RECOG_INTERCO_FLAG

p_Inventory_Item IN NUMBER

RETURN VARCHAR2

-- **** RETURNS Y IF COGS RECOG IS ON INTERCOMPANY

xyz_cogs_recog_interco_flag VARCHAR2(1);

xyz_cogs_recog_interco_flag:='N';

SELECT

/*+ ORDERED */

xyz_cogs_recog_interco_flag

mmt.transaction_id = p_transaction_id -- **** COGS RECOG TRANSACTION

-- **** THIS WILL PULL IN THE SOURCE TRANS OF COGS RECOG

EXISTS

SELECT

/*+ ORDERED */

mmt2.transaction_id

mtl_material_transactions mmt2

, inv.mtl_transaction_types ttype

mmt2.transaction_source_id = mmt.transaction_source_id

-- **** THERE COULD BE MULTIPLE ITEMS WITH DIFFERENT SOURCES

mmt2.inventory_item_id = mmt.inventory_item_id

ttype.transaction_type_id = mmt2.transaction_type_id

-- **** 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 '

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

xyz_no_markup_inv_cost NUMBER;

xyz_no_markup_inv_cost := 0;

SELECT

/*+ ORDERED */

ROUND (

( mmt3.intercompany_cost

( mmt3.intercompany_cost - ( rates.conversion_rate * mmt1.actual_cost ) )

* mmt3.transaction_quantity

) extend_inv

xyz_no_markup_inv_cost

, gl_daily_rates rates

mmt.transaction_id = p_transaction_id

-- *********************************************

ttype1.transaction_type_name = 'Sales order issue'

-- *********************************************

ttype2.transaction_type_name = 'Logical Intercompany Sales Issue'

-- ***************************************************

-- *********************************************

-- **** WE NEED TO CONVERT THE SHIP AMT TO THE RECEIPT CURRENCY

rates.from_currency = mmt2.currency_code

rates.to_currency = mmt3.currency_code

rates.conversion_date = TRUNC (mmt.transaction_date)

--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 '

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

xyz_markup_inv_cost NUMBER;

xyz_markup_inv_cost := 0;

SELECT

/*+ ORDERED */

ROUND (

( mmt2.actual_cost * mmt2.transaction_quantity )

---- **** MUST ROUND SEPERATELY FROM SUBTRACT SO ENTRIES BALANCE WITHOUT ROUNDING ERROR

ROUND (

( mmt3.actual_cost *

( mmt2.actual_cost / mmt2.intercompany_cost )

) markup

xyz_markup_inv_cost

, inv.mtl_transaction_types ttype

, inv.mtl_transaction_types ttype2

ttype.transaction_type_id(+) = mmt2.transaction_type_id

ttype2.transaction_type_id(+) = mmt3.transaction_type_id

-- ************************************

' 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;

PL/SQL Function - XYZ_INTERCO_SEGMENT

CREATE OR REPLACE

FUNCTION XYZ_INTERCO_SEGMENT

RETURN VARCHAR2

xyz_interco_segment VARCHAR2(3);

xyz_interco_segment:='000';

SELECT

/*+ ORDERED */

comb.segment1

xyz_interco_segment

, mtl_transaction_types ttype

, gl_code_combinations comb

-- **** INTERNAL DROP SHIP INTERCOMPANY TRANS

ttype.transaction_type_id = mmt.transaction_type_id

-- ****

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;

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

-- **** THIS IS USED BY INTERNAL DROP SHIPS TO ADJUST THE

-- **** CUSTOMER FACING SIDE OF THE TRANSACTION

SELECT

/*+ ORDERED */

ROUND (

) extend_inv

mmt.transaction_id = p_transaction_id -- **** COGS RECOG

-- **** THIS WILL PULL IN THE SOURCE TRANS OF COGS RECOG

mmt1.transaction_source_id = mmt.transaction_source_id

-- **** THERE COULD BE MULTIPLE ITEMS PER ORDER

mmt1.inventory_item_id = mmt.inventory_item_id

-- *********************************************

mmt2.parent_transaction_id = mmt1.parent_transaction_id

-- ***************************************************

mmt3.parent_transaction_id = mmt1.parent_transaction_id

-- *********************************************

-- ************************************

' XYZ_INTRNL_DROP_COGS_AMT '

-- ************************************

EXCEPTION

WHEN OTHERS THEN

' XYZ_INTRNL_DROP_COGS_AMT '

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

-- **** THIS IS USED BY INTERNAL DROP SHIPS TO ADJUST THE

-- **** CUSTOMER FACING SIDE OF THE TRANSACTION

SELECT

/*+ ORDERED */

ROUND (

) extend_inv

-- *********************************************

-- ***************************************************

-- *********************************************

-- ************************************

' XYZ_INTRNL_DROP_INV_AMT '

-- ************************************

EXCEPTION

WHEN OTHERS THEN

' XYZ_INTRNL_DROP_INV_AMT '

White Paper Subledger Accounting for Intercompany Transaction Flows V5.6

Documents

Inventory Subledger Standard - AICPA...The Inventory Subledger ADS is intended to accommodate basic analysis of the inventory process. The ... The Inventory Subledger Standard audit

Cloud Oracle Financials...Oracle Financials Cloud Implementing Subledger Accounting Glossary 60 subledger journal entry A detailed journal entry generated for a transaction in a subledger

CHAPTER 10: MULTICOMPANY OPERATIONS - INTERCOMPANY · Chapter 10: Multicompany Operations - Intercompany 10 - 5 Set up the Intercompany Partner The first step in setting up Intercompany

Subledger accounting

DB Installation Manual Wise v5.6 v1.0

What\'s New in Sage Accpac v5.6

S/4HANA Financial Products Subledger

Reconcile Subledger vs General ledger

Subledger Accounting Implementation Options

Fixed Asset Subledger Standard - AICPA

CoreUARTapb v5.6 Handbook

Fact Sheet Intercompany Solution Overview Intercompany ...€¦ · Intercompany Workflow: Allow a business entity to accept or reject incoming intercompany transactions, and notify

Intercompany NLCC

Accounts Receivable Subledger Standard - AICPA

Accounts Receivable Subledger Standard

Intercompany setup

Intercompany Accounting for Internal Order and Drop … SIG Minutes/Intercompany... · Intercompany Accounting for Internal ... •By enabling advanced accounting for an intercompany

Intercompany EDI

Call of Cthulhu Rulebook v5.6

15720525 Oracle Subledger Accounting