Roles on the elimination of inter-unit transf. assets

Hi guys
We have a problem on implementing IU elimination of profit on assets. Our requirement is not to use capitalisation and valuation allowances. This role is left empty. Upon saving there are various warning messages coming up regarding roles for characteristics that can not be filled. When the databasis is exited and re-entered, the capitaisation and valuation fields are filled with the non-current asset value giving rise to an error message. Message number UCM0145 stating that the caharcteristics for non-current assets and assets / liabilities are identical. What are the steps to get past this error and why is this field filled even though we are not using it in the data streams?
Thanks.

1. It is necessary to create a InfoObject Catalog for this, or include the onject within the already created catalog. In my case I included all to get around the errors:
a.     0BCS_FVD with compound object of MCOMPANY
b.     0BCS_AASSET (or equivalent M-object)
c.     0BCS_AASTMN (or equivalent M-object)
d.     0BCS_ALMCOM (or equivalent M-object)
e.     0BCS_ALMPC (or equivalent M-object)
f.     0BCS_ALMU (or equivalent M-object)
g.     0BCS_ALTYPE (or equivalent M-object)
h.     0BCS_ASSET (or equivalent M-object)
i.     0BCS_FVDMN (or equivalent M-object)
j.     0BCS_INITEM (or equivalent M-object)
k.     0BCS_MASSET (or equivalent M-object)
l.     0BCS_MASTMN (or equivalent M-object)
2. Maintain the necessary customizing for Assets/Liabilities in Data Basis on Tab Data Model for Asset/Liability-managing Consolidation Unit, Elimination of Interunit Profit/Loss in Transferred Assets and Capitalization and Valuation Allowances. For further details please also review SAP note 1082379.
3. Add the data steams for Assets/Liabilities and Noncurrent Assets
4. Save and generate the data basis
NOTE: If the data basis is changed and needs to be regenerated, there is a possibility that the error below will occur.
Data model: Definitions of acquired asset and retired asset are invalid
Message no. UCM0149
When this error occurs, the steps to save the data basis without the error are:
a. Make Retired u201CNoncurrent Assetu201D blank
b. Save the data basis
c. The system will automatically add the characteristic from u201CNoncurrent Assetu201D to u201CRetired Noncurrent Assetu201D

Similar Messages

Inter unit transfer -stock transfer

Hi
what is the difference between Inter unit transfer & stock transfer between plants

Hi,
Intra company transfer - transferring stocks between plant under the same company code. So u can do that with delivery and without delivery also. But billing will not happen.
Inter company transfer - transferring stocks from one company code o another company code. So u can do this without delivery and with delivery and billing. Below i have given configuration steps for both.
Follow the below steps to to make STO between two plants ( different company codes).It is also called as Inter Company STO.....
1) Create one Customer Master in XD01 with respect to Supplying Plant Sales Area and assign this Customer no with Receiving Plant in OLME->PO-> set up STO->Define shipping data for plant and for the supplying Plant assign the above sales area.( Make sure, In Customer Master, sales Area Tab: you are maintaining shipping condition)
2) For Receiving Plant Pur. Org and Co.Code Combination create Vendor master in XK01 and in this vendor master assign the Supplying plant in Pur.Org.Data screen->Extras--> Add.Pur.data
3) OLME->PO-> Set up STO------>For your supplying plant assign document type NB, Delivery type NLCC and Checking Rule RP
4)then For your supplying Plant and receiving Plant assign Document type NB
5)Make sure you are maintaining Sales View for the material at supplying Plant and in Sales /Gen plant Data view maintain Availability check, Loading group and Transportation group.
6) In SPRo-->Logistics execution> Shipping->Basic shipping functions->Shipping point Determination>assign shipping points-> For your Loading group, Shipping Condition and Supplying plant combination, Assign shipping point
these are the configuration settings you have to do in background.
Then Create STO from Receiving Plant in ME21N with document type NB.
Based on that STO, Create Delivery in VL10B from supplying Plant
Do PGI in VL02N from Supplying plant
Do GR in MIGO at Receiving Plant keeping Outbound delivery as a ref. document.
Now your STO bet. two plants belongs to diff. Co.Codes will be completed.
2)Follow the below steps to to make STO between two plants belongs to same company codes).It is also called as Intra- Company STO.....**
1)Create one Customer for Supplying Plant Sales area and assign this Customer no with Receiving Plant in OLME---> PO -
> Set up STO -
> define Shipping Data for plants. and maintain the same sales area in your Supplying plant.
2) In OLME---> PO -
> Set up STO.....for your Document Type: UB and Suppying plant Combination assign Del. Type NL and Checking rule RP
3) In OLME---> PO -
> Set up STO...for your Supplying Plant and Receiving Plant combination Maintain Doc. Type : UB
Make sure you are maintaining Sales View for your Material at Supplying Plant.
4) Maintain Shipping point at, SPRO----> Logistics Execution -
> Shipping -
> Basic Shipping Functions -
> Shipping Point Determination for Plants.....there for your Loading group, Shipping Condition, Shipping Plant combination maintain Shipping plant..
Now Create STO in ME21N with Doc.type: UB at Receiving Plant.
Then Create Delivery in VL10B from Supplying Plant...
Then Do PGI in VL02N from supplying Plant.
Then do GR at Receiving Plant based on Outbound Delivery at Receiving Plant...
Regards,
Prasath

What is the difference between Inter-org Transfer & ISO

Can anybody please share the difference between Inter-org Transfer & ISO?
e.g. Legal bounding, accounting entries, traceability, charging to demanding entity/organization...
Also please help me to understand when shall we use which option, and where we can not use which option...
e.g. Inter-org transfer can't be used when material in required in some different LE (Legal entity).

Internal Sales Order (ISO) is the same as the PO and SO creation process which occurs within the Company. It is a process used to request and transfer material from one inventory to another with the Same or Different Operating Unit. This is usually initiated in Oracle Purchasing which creates a Requisition and upon running the Create Internal Sales Order Concurrent program, the order is loaded into the Order Import Tables. The Order Import program is run in the Order Management of the Operating Unit in which the Orders needs to be Created. The Order is then booked and shipped and received in the destination organization. The invoicing activity depends on the company rules.
Inter Org Transfers are the material transfers within two Organizations that are under the same Operating Unit. There is no creation of the sales orders or anything but a regular material transfer from one org to another. The item needs to be defined in both the Organizations. This is usually done to maintain the inventory balances and there is no actual shipping process that is defined for this.

How to receive intransit shipments for inter-organization transfer with in-transit receipt routing via Receiving Open Interface

Somebody have samples about how to fill the ROI tables only to have the receipt from inter-organization transfer with in-transit routing.
Thanks in advance.

Pl. visit following links.
Oracle Apps: 11.5.10 / R12 ROI How to Receive Intransit Shipment (Inter-org transfer) for Lot / Serial Controlled Items …
11.5.10 ROI를 통해 INTRANSIT SHIPMENT(INTER-ORG TRANSFER)를 처리하는 방법

SEM-BCS: Cons Group Field Required for Inter-Unit Elimination

Hi!
I need help.
I need to use document type for manual postings that allows me to indicate the cons group field.
I understand the PL10 is cons unit dependent only and not cons group.
I know that PL12 allows cons group posting.
But from what I understand PL12 is not captured in the inter-unit elimation task.
Is there other way?
Appreciate response.

Hi Adam and Eugene,
Thanks for the helpful response.
However I want my manual entries related to inter-unit elimination to reflect in one cons group only, considering that we have different hierarchies in our system.
The manual entries related to I/U elimation is basically an adjustment to the intercompany accounts. The purpose of my manual entries is to minimize the value of the difference of my intercompany accounts.
for example: (before interunit elimination)
Company A has intercompany accounts receivable of 100 USD with trading partner Company B
However, Company B recorded 50 USD intercompany payable with trading partner Company A. Company B has understated figure of 50 USd
To manually adjust in the BCS system, I'll post in Company B debit inventory and credit intercompany payable 50 with trading partner Company A.
Question is I want my adjusting entries to relfect only at the top hierarchy (one cons group) and not at the other cons group
Is there a way?
Please advice.
Thank you so much

HFM "Inter unit profit elimination"

Can any one have any idea about " Inter unit profit elimination" and how it is done in HFM? we have done this through Essbase, and we just converted to HFM

If I understand your terminology correctly, this is simply 'Intercompany'!
HFM has an out the box ICP dimension.
When you create your Entity ad Account hierarchies, simply flag them as ICP and they will automatically eliminate and, the system report will provide Intercompany matching.
No more... no less. HFM is the right place to do this. As you seem to have done, in Essbase you have to script it.
Good luck

Inter Unit Elimination

Hi,
Can any body explain, what is inter unit elimination in consolidation and why this has to be carried out, with simple example?
Regards,
Praisty

IC elimination has to do with group reporting. If 2 business units are part of same group. And there is a business transaction between them. For example, one business unit sells goods or services to the other. This transaction will not result in any net profit/loss or even net asset/liablity situation at the group level, where we have to report on the consolidated basis.
The popular way to achieve this in SAP is to use trading partner for these transactions. And during consolidation these lines with TP will be eliminated while generating the periodic consolidated reports.
Thanks
Ron

Split transfer order on the basis of Storage Unit type(SUT)

Hi,
I got one problem and want the solution for that immediately.the problem is as follows:-
The transfer Order needs to be split by quantity according to the quantity per Storage Unit Type.
I have to do this making chages in the SAP standard user Exit EXIT_SAPLL03A_12 in the program SAPML03T.
Eg.One scenario is provided
Scenario 1: Perform transaction MIGO with a movement type 101 for Outbound Delivery 80000201. Enter a quantity of 15 kgs.
the result should be as follows:
Scenario 1: Check TOs created by going to transaction LT22. Enter Warehouse number 200; Storage type 902. Select the Dynamic Selections button and select Transfer order Item. Double click on Material and enter the material number (W075006). The SUT is 5kg so the expected result is for 3 TOs to have been created.
Means one TO got splitted in 3 TOs.
Please provide me the help.

Hi Vinay,
This can be done purely through customizing. Please check IMG -> Logistics Execution -> Warehouse Management -> Activities -> Transfers -> Processing Performance Data/Split. You will need to define a sorting profile for TO split in where LETYP (storage unit type) can be used as sorting condition. The sorting profile should then be assigned to defined TO split.
Hope it helps.
Have a nice weekend!

Inter unit profit elimination

Hi all
This is not a technical question ...Can any one have any idea about " Inter unit profit elimination" and "Driver Models" what exactly these words represent....is it possible to achieve using Hyperion planning.
Thanks

Technically yes, you can do these kind of entries.
However, since these entries are almost journal entries, users should be doing these in another system like HFM. This being said, I am seen implementation where users have use essbase for these kind of entries.

Inter-Organization transfer is not being possible..any workaround?

We were using Inter ORG transfer whiich is a seeded function in Oracle Inv module to transfer material from ORG A to ORG B
Navigation
(N)Inventory>Transactions>Inter-Organization Transfer
Now the problem is our items are not centralised.That is For example an item semi-conductors has a different item code opened for ORG A and a different for ORG B
Suppose ORG A code is SCND.000001
and ORG B code is SCND.000002
we have a two segment item flexfield
When ORG A tries to ship to ORG B, it doesnt appear in InterORG form since an item has to be enables in both the ORGS, source and detination, and since opur items are not centralised thats not possib
So what the user does is assigns the itemcode associated with his ORG to the Destination ORG too
Now when the Destination ORG receives the shipment , he has to receive in the new code assigned to him..Now has a result he has two codes which means reporting gets disturbed, history is difficult to find, manageability becomes hard..
Could you please suggesta workaround for this

Sandeep Gandhi, Independent Consultant wrote:
Any workaround is going to be hard and cumbersome. And that is because you are running counter to the industry practice of having the same item number across for the same item in your organizations? What is the second segment for? Is it a revision of sorts?We have 3 segment item categories
only the first segment is used , ACCS for accessory items, CHEM for chemical items, MECH for mechanical items
and in item, the first segment is used to represent the category the item belongs to
like ACCS or CHEM or MECH
than each new item is incremented by 1 in second segment, like ACCS.000001, next one would be ACCS.000002 and so on
We have more than 150,000 items and duplication cannot be eliminated, but it can be reduced..any advices for it??
>
One of the workaround will be to receive SCND.0002 and then do a RE-ID transaction (i.e. issue out 0002 and issue in 0001). But you will still need some kind of custom reports /screens if you need to tie the history together.I have already given this workaround but this is not acceptable and effective
Can we use internal requisitions?? i guess we cant without OM? right?

11.5.10 ROI를 통해 INTRANSIT SHIPMENT(INTER-ORG TRANSFER)를 처리하는 방법

제품: Applications
작성날짜 : 2006-05-30
11.5.10 ROI를 통해 INTRANSIT SHIPMENT(INTER-ORG TRANSFER)를 처리하는 방법
===============================================================
PURPOSE
11.5.10 Receiving Open Interface를 통해 Lot / Serial Controlled Items을 Intransit Shipment (Inter-org transfer) 처리하는 방법을 기술함.
Explanation
11.5.10에서는 ROI를 통해 Inter-Org Transfers를 지원합니다.
. RECEIVE transaction
. DELIVER to Inventory Transaction
Solution
========
- Receiving Open Interface (ROI)를 통해서 2 inventory organizations
사이의 Inter-Organization Transfer를 수행한다.
- Direct Receipt Routing으로 RECEIVE 와 DELIVER transaction을 동시에
수행한다.
<1> the sample script has been tested for a Lot and Serial
Controlled Item.
The script will load records into the tables
RCV_HEADERS_INTERFACE,
RCV_TRANSACTIONS_INTERFACE,
MTL_TRANSACTIONS_LOTS_INTERFACE
MTL_SERIAL_NUMBERS_INTERFACE
* If the item is only a standard item, only the records into
RCV_HEADERS_INTERFACE and RCV_TRANSACTIONS_INTERFACE tables
have to be created.
<2> Setup
1) Inventory Setup/Organizations/Shipping Networks
- From Sending Organization M1 to Destination Organization D2
- Transfer Type=Intransit
- Receipt Routing=Direct
2) Item 'Lot-Serial-Controlled-1' is a lot and serial controlled
Item in sending and Destination Organization
<3> Create manual "Intransit Shipment"
Inventory / Transactions/ Inter Organization transfer
- From Org= M1, To Org= D2
- Shipment: 'ROI-Lot-Serial-1'
- Item= Lot-Serial-Controlled-1
- Lot=S00226
- From Subinventory=Stores
- To Subinventory=Staging1
- Quantity=10
- Start Serial Number=SM1_00001
- End Serial Number=SM1_00010
<4> data collection for RCV_TRANSACTIONS_INTERFACE table
- Select * from RCV_SHIPMENT_HEADERS
where SHIPMENT_NUM like '&Shipment_Num';
- Select * from RCV_SHIPMENT_LINES
where SHIPMENT_HEADER_ID=&Shipment_Header_id;
- Select * from RCV_LOTS_SUPPLY
where SHIPMENT_LINE_ID=&Shipment_Line_id;
- Select * from RCV_SERIAL_SUPPLY
where SHIPMENT_LINE_ID=&Shipment_Line_id;
<5> RECEIVE/ DELIVER to INVENTORY Transaction for INTER-ORG
TRANSFER SHIPMENT
- Direct DELIVER Receipt
- LOT_NUM=S00226 and serial numbers SM1_00001 to SM1_00002
Insert
- RCV_HEADERS_INTERFACE with SHIPMENT_NUM='ROI-Lot-Serial-1',
VALIDATION_FLAG='Y'
- RCV_TRANSACTIONS_INTERFACE with TRANSACTION_TYPE='RECEIVE',
AUTO_TRANSACT_CODE='DELIVER' , DESTINATION_TYPE_CODE='INVENTORY'
RECEIPT_SOURCE_CODE='INVENTORY', SOURCE_DOCUMENT_CODE='INVENTORY'
VALIDATION_FLAG='Y'
- MTL_TRANSACTIONS_LOTS_INTERFACE with quantity=2, lot number S00226
- MTL_TRANSACTIONS_SERIAL_INTERFACE with FM_SERIAL_NUMBER='SM1_00001'
and TO_SERIAL_NUMBER='SM1_00002'
INSERT INTO RCV_HEADERS_INTERFACE
(HEADER_INTERFACE_ID,
GROUP_ID,
PROCESSING_STATUS_CODE,
RECEIPT_SOURCE_CODE,
TRANSACTION_TYPE,
AUTO_TRANSACT_CODE,
LAST_UPDATE_DATE,
LAST_UPDATED_BY,
LAST_UPDATE_LOGIN,
CREATION_DATE,
CREATED_BY,
SHIPMENT_NUM,
SHIP_TO_ORGANIZATION_ID,
EXPECTED_RECEIPT_DATE,
VALIDATION_FLAG
VALUES
(rcv_headers_interface_s.nextval , --Header_Interface_Id
rcv_interface_groups_s.nextval, --Group_Id
'PENDING', --Processing_Status_Code
'INVENTORY', --Receipt_Source_Code
'NEW', --Transaction_Type
'DELIVER', --Auto_Transact_Code
SYSDATE, --Last_Update_Date
0, --Last_Updated_By
0, --Last_Update_Login
SYSDATE, --Creation_Date
0, --Created_By
'ROI-Lot-Serial-1', --Shipment_Num
210, --Ship_To_Organization_Id,
SYSDATE, --Expected_Receipt_Date
'Y' --Validation_Flag
INSERT INTO RCV_TRANSACTIONS_INTERFACE
(INTERFACE_TRANSACTION_ID,
GROUP_ID,
LAST_UPDATE_DATE,
LAST_UPDATED_BY,
CREATION_DATE,
CREATED_BY,
LAST_UPDATE_LOGIN,
TRANSACTION_TYPE,
TRANSACTION_DATE,
PROCESSING_STATUS_CODE,
PROCESSING_MODE_CODE,
TRANSACTION_STATUS_CODE,
QUANTITY,
UNIT_OF_MEASURE,
INTERFACE_SOURCE_CODE,
ITEM_ID,
EMPLOYEE_ID,
AUTO_TRANSACT_CODE,
SHIPMENT_HEADER_ID,
SHIPMENT_LINE_ID,
RECEIPT_SOURCE_CODE,
TO_ORGANIZATION_ID,
SOURCE_DOCUMENT_CODE,
DESTINATION_TYPE_CODE,
SUBINVENTORY,
SHIPMENT_NUM,
EXPECTED_RECEIPT_DATE,
HEADER_INTERFACE_ID,
VALIDATION_FLAG
VALUES
( rcv_transactions_interface_s.nextval, --
INTERFACE_TRANSACTION_ID
rcv_interface_groups_s.currval, --GROUP_ID
SYSDATE, --LAST_UPDATE_DATE
0, --LAST_UPDATED_BY
SYSDATE, --CREATION_DATE
0, --CREATED_BY
0, --LAST_UPDATE_LOGIN
'RECEIVE', --TRANSACTION_TYPE
SYSDATE, --TRANSACTION_DATE
'PENDING', --PROCESSING_STATUS_CODE
'BATCH', --PROCESSING_MODE_CODE
'PENDING', --TRANSACTION_STATUS_CODE
2, --QUANTITY
'Each', --UNIT_OF_MEASURE
'RCV', --INTERFACE_SOURCE_CODE
169845, --ITEM_ID
13706, --EMPLOYEE_ID
'DELIVER', --AUTO_TRANSACT_CODE
233534, --SHIPMENT_HEADER_ID
246486, --SHIPMENT_LINE_ID
'INVENTORY', --RECEIPT_SOURCE_CODE
210, --TO_ORGANIZATION_ID
'INVENTORY', --SOURCE_DOCUMENT_CODE
'INVENTORY', --DESTINATION_TYPE_CODE
'Staging1', --SUBINVENTORY
'ROI-Lot-Serial-1', --SHIPMENT_NUM
SYSDATE, --EXPECTED_RECEIPT_DATE,
rcv_headers_interface_s.currval, --HEADER_INTERFACE_ID
'Y' --VALIDATION_FLAG
INSERT INTO MTL_TRANSACTION_LOTS_INTERFACE
( TRANSACTION_INTERFACE_ID,
LAST_UPDATE_DATE,
LAST_UPDATED_BY,
CREATION_DATE,
CREATED_BY,
LAST_UPDATE_LOGIN,
LOT_NUMBER,
TRANSACTION_QUANTITY,
PRIMARY_QUANTITY,
SERIAL_TRANSACTION_TEMP_ID,
PRODUCT_CODE,
PRODUCT_TRANSACTION_ID
VALUES
( MTL_MATERIAL_TRANSACTIONS_S.NEXTVAL,--
TRANSACTION_INTERFACE_ID
SYSDATE, --LAST_UPDATE_DATE
0, --LAST_UPDATED_BY
SYSDATE, --CREATION_DATE
0, --CREATED_BY
0, --LAST_UPDATE_LOGIN
'S00226', --LOT_NUMBER
2, --TRANSACTION_QUANTITY
2, --PRIMARY_QUANTITY
MTL_MATERIAL_TRANSACTIONS_S.NEXTVAL, --
SERIAL_TRANSACTION_TEMP_ID
'RCV', --PRODUCT_CODE
RCV_TRANSACTIONS_INTERFACE_S.CURRVAL --
PRODUCT_TRANSACTION_ID
INSERT INTO MTL_SERIAL_NUMBERS_INTERFACE
( TRANSACTION_INTERFACE_ID,
LAST_UPDATE_DATE,
LAST_UPDATED_BY,
CREATION_DATE,
CREATED_BY,
LAST_UPDATE_LOGIN,
FM_SERIAL_NUMBER,
TO_SERIAL_NUMBER,
PRODUCT_CODE,
PRODUCT_TRANSACTION_ID)
VALUES
(MTL_MATERIAL_TRANSACTIONS_S.CURRVAL,--
TRANSACTION_INTERFACE_ID
SYSDATE, --LAST_UPDATE_DATE
0, --LAST_UPDATED_BY
SYSDATE, --CREATION_DATE
0, --CREATED_BY
0, --LAST_UPDATE_LOGIN
'SM1_00001', --FM_SERIAL_NUMBER
'SM1_00002', --TO_SERIAL_NUMBER
'RCV', --PRODUCT_CODE
RCV_TRANSACTIONS_INTERFACE_S.CURRVAL --
PRODUCT_TRANSACTION_ID
Commit;
<6> In Purchasing Responsibility, Change to receiving organization
- run the Receiving Transaction Processor for the given group_id
used in RHI and RTI (GROUP_ID=25168)
<7> check a data
Navigate to Receiving / Receiving Transactions Summary form
- For Shipment Number ROI-Lot-Serial-1, Receipt Number 5012
has Receive and Deliver transactions.
Reference Documents
Note#336924.1
글 수정:
heeyeol2

I Think Rajesh is Good inspite of Merlin.
Can u send me your mail i'd.
Actually I'm Facing Some Proble In Receipt Header.
As the period in GL and Inventory is open till march-07 and i'm doing transaction today.
After this also application is throughing a error.
APP-PO-14230
I Can't Send u the Screen Short hear.
Please Help Me.
Bachan

Handling unit transfer (311 move) using bapi_goodsmvt_create

MII is using bapi_goodsmvt_create to do a 311 type Handling unit movement. While BAPI is successful and returns a response back as "Delivery 80817152 created". But in ERP, this BAPI is creating a outbound delivery while it should be inbound delivery.
So basically transfer is not happening there if I check in humo.
If Movement Indicator is set to "I" in BAPI request than ERP sends error message " Update control of movement type is incorrect (entry 311 XX_I)
I would like to know if some body has experienced the same issue & has any resolution and also want to confirm that handling unit transfer is possible with bapi_goodsmvt_create.
Thanks a lot
Regards
Ram Upadhayay

This BAPI only conducts goods movements. It does not affect the handling unit.
If you want to process a handling unit you must use a different BAPI. Are you attempting to unpack the HU?
Use BAPI_HU_UNPACK.

How can we reverse an inter-org transfer?

Hi
We have a problem with an inter-org transfer. The intransit shipment has been created to an intransit receipt and the receipt didnt create "RECEIVE" and "DELIVER" transactions. It only created "RECEIVE" so we corrected the quantity and made the receipt to zero.
The problem now is this item/receipt is shown in the expected receipts report.
How can we reverse or cancel the shipment?
Any ideas please?
Thanks,
Prathima

Prathima,
What metalink says is correct.
Option 1: Deliver it in the destination and reverse the transaction by doing one more org transfer from B to A. Clean way.
Option 2: If your FOB point in the shipping network is Receiving, then you can probably apply a data script. You need to delete the mtl_supply and then perform miscellaneous receipt crediting intransit account and debiting inventory account. If your FOB point is shipping, your accounting has touched more accounts (if transfer pricing is involved even one more) hence this method is not recommended.
I am not sure how many more applications you have in your instance that are dependent like manufacturing and service applications.
If they are installed, as you can see the first approach is clean.
Thanks
Nagamohan

Inter unit posting for blank business area

Hi
For Inter unit posting we have executed the run in TC-F.5D & F.5E for the month april -- july which was successful.But while executing the same for the month of aug it is reading the document to be posted for IU run.But while executing f.5E it not generating the posting.Please adivice the possible reason for the same problem.Please consider it as a priority.
Thanks
shivaji

Hi,
I have an answer for your 1st question only.
After putting the data in F.01 click on the "Arrow" which is there beside the option Business Area which will take you tor "Multiple selection for Business Area" window.
In that window do not enter anything but select the 3rd option, "Maintain selection options". you will get one more window with the options 1. Single Value 2. Greater than or equal to and so on......
Select, 1st option, Single Value and execute (F8). Also select - "Classical List" option under List Output in F.01, you will be able to see "Non Business Area" related GL's in Balance Sheet.
Regards,
Shridhar Sawant
FICO

Raising receipt for Inter-Org transfer

Hi,
Is there any API for inventory Receipt creation for Inter-Org transfer.
I have gone through Receving Open Interface, Oracle Inventory Open Interface and API Volume II(manual), it specifically says "Receiving Open Interface does not support:Receiving against Inter-Organization transfers".
If any one has worked on this kind of assignment before ,please provide information.Your help is appreciated.
Thanks
Ravi

Thanks for your reply Kashif,but the link you provided doesn't explain what source_code should be for an Inter Org Transfer
Edited by: sandy on Oct 13, 2011 12:19 PM

Roles on the elimination of inter-unit transf. assets

Similar Messages

Maybe you are looking for