ABUMN Intracompnay asset transfer error AA389 Transaction type 300 not pos

Hello,
I am getting the following error message while runinng ABUMN Transaction type 300 not possible (no affiliated company specified) Message no. AA389. Transfer variant 4 (transfer within a company) code is set as follows
Rel Type               Crs-sys.ar     Rel.crsyst area     trans me              retmt tr type   acq.trasn.typ
1                                   *                generic entry              1                        300                 310
2                                   *                 generic entry             2                        300                 310
The problem is that on t-code AO76   trans type 300 Posting type has "Post to affiliated company" and "Post gross" both checked on. In Company Code Global Data my Company code and Company are the same.
Transaction type 306 has posting type "Do not post to affiiliated co." and "Post net" checked on.
I changed transfer variant 4 to have retmt transaction type of 306 for relationship type 1 and 2 instead of 300 and I do not get an error and the posted depriciation is updated correctly.
Since 300 is the recommended SAP setting in note 327088 would their be any problem if I leave it at 306?
Thanks for any answers to this issue.

Hello Murali,
Thank you for your response.
I created a new tranaction type which was a copy of 300 and clicked on
Do not post to affiliated company
Post Net
Since 300 was set up for intercompany and it resolved my issue.
Rgds,
Dan

Similar Messages

ABT1N Intercompany Asset Transfer error: AA390   T type 230 not possible

Dear experts,
I am trying to post an intercompany asset transfer with trx code ABT1N but when simulating the error code
Transaction type 230 not possible (posting to affiliated company) appears. This is the explanation of the error:
Message no. AA390
Diagnosis
     For the current document, you specified either implicitly (via the
     customer/vendor), or explicitly (with a manual entry), that this posting
     is to an affiliated company. In this case, Asset Accounting requires you
     to use special transaction types. This enables the system to separately
     identify such transactions.
I do not understand the error because TType is "Retirement to affiliated company with revenue" so should be correct.
Does anybody know what could be wrong?
Cheers

Hi
Firstly, check out Note 209643.
Secondly, please read the long text of the error message again. The
transaction type must be set as "post to affiliated company". And
you must check back the followings :-
1. Please execcute function: SAP IMG -> FI -> asset accounting ->
    transaction -> specify default transaction type.
    You can find the default transaction type for "retirement from
    inter-company transfer" and "acquisition from inter-company
    transfer".
Then check in their definition whether they are relevant to
    affiliated company.
If they are NOT RELEVANT to affiliated company, you can
    substitute them with other transaction type Relevant to affiliated
    company.
2. Please check the definition of transfer variant. In the transfer
    variant, you have assigned the transaction type for both retirement
    and acqusition for relation type 1. Both transaction types should be
    set as "post to affiliated company" .
Please note that the abovementioned points must be checked because
the system logic will check the validity of the default value in
Point 1.
Then the transaction type in the point 2 will be used instead and
re-checked again.
Have you try to use 'No Reveune' in the specification for revenue?,
I think if it is afflicated companies, you are not allowed to use
revenue.
This error can also be produced because a wrong definition of the trans-
fer variants. Please have a look on note 327088 for further details.
Most of the issues on this matter were solved with this last Note.
Cheers, Blaz

FBV1 error - Transaction Type 030 not possible

Hi SAP experts,
I am currently facing an issue while in FBV1 (via batch input)
It displays error message Transaction Type 030 not possible (posting to affiliated company), however, the asset group that it belongs to can only be Type 030 (Acquisition in group area only).
How can this be fixed?
Is there another TType that is similar to 030 ?
Any help is welcome
Regards
Roger

Hi,
check SAPNET note 127650.
Best regards

Transaction type ZGC not possible (posting to affiliated company) in ABSO

Hi all,
We have depreciation areas 01, 30, 31, 32 .
dep area 30, 31, 32 inherits the values from 01.
We want to post credit value to dep area 01 after doing the aqusition .
Hence we created a seperate transaction type ZGC ( in aqusitions- Tcode AO73) and limited it to dep areas 01, 30, 31, 32.
Transaction type ZGC is having credit and " do not post to affliated company " radio button is selected.
Now the issue is when we run ABSO to do a credit post in dep area 01 we are getting the below error .
Transaction type ZGC not possible (posting to affiliated company)
Message no. AA390
Diagnosis
For the current document, you specified either implicitly (via the customer/vendor), or explicitly (with a manual entry), that this posting is to an affiliated company. In this case, Asset Accounting requires you to use special transaction types. This enables the system to separately identify such transactions.
Procedure
Check the line items that you have already entered, and the transaction type you entered.
Not sure why it is asking for affliated company .
It will be great if any one help on this why we are getting this issue.

Hi Daya,
Please try to choose Trans.Type 100 in AO73 transaction code and select the radio button Post to affiliated company under Posting type.
Thanks,
Kumar

Transaction type 100 not posible (posting to affiliated company)

Hil
While asset acquistion posting in f-90 ia geting error message "Transaction type 100 not posible (posting to affiliated company)"
can you please give solution for this one

Hi
pl check following settings in spro Img->Financial Accounting-Asset Accouning----Transctions--Acquisitions-Define Transaction Types for Acquisitions-in choose activity window -dbl clk on "Define Transaction Types for Acquisitions"
select transaction type 100--click on details--check posting type. if " Do not post to affiliated company." is selected then choose another transaction type which allows acquisition with option "Post to affiliated company"
regards
Vishwas
Edited by: Vishwas_bapat on Mar 24, 2011 1:24 PM

Transaction type 230 not possible (no affiliated company specified) inABT1N

Dear Experts,
While I am posting transaction through ABT1N i am getting an error message
Transaction type 230 not possible (no affiliated company specified)
Message no. AA389
I checked in the transaction type 230 but here posting to affiliated co tick is their.Please advice at an earliest.
Regards,
Rahul

Hi,
Refer this thread Problum in ABT1N
Regards
GK

AA390 Transaction type 345 not possibel to post to affiliate company

Hi,
We are getting this error AA390 transaction type 345 not possible to post to affiliate company , while settling an AuC to a fixed asset using trx AIAB.
Please advise how this can be resolved or any config steps are missing for TTypes 345 or 346.
Thanks,
Manohar

Hi,
Check in transaction type 345/346, Radio Button for Post to Affiliate Company is selected. In case its not, please select the radio button and then try again.This should work.
By default, Post not to affiliated company is selected.
Hope this helps.
Regards,
Harish

Posting with trans.type 300 not possible (No acquisition posted)

Dear Gurus,
When I execute the T-code ABUMN, i've got the following message:
Posting with trans.type 300 not possible (No acquisition posted)
Message no. AA324
Diagnosis
Transaction type 300 belongs to a transaction type group, which can only
be used to post to assets to which posting has already been performed.
However, no postings have been made to this asset.
Procedure
Use a transaction type from a transaction type group, which can be used
for the first acquisition to an asset.
Regards

Hi sapraj ,
Transaction type 300 is "transfer of retire. old assets data from cap. asset" ,which means before you transfer this asset, it has to be first capitalized , for asset capitalization, you may use transaction type 100
Mu

Message no. AK005 - Asset is investment measure, transaction type not allow

Dear All,
I am getting following error while transfering Investment AuC to Main Asset.
Message no. AK005 - Asset is investment measure, transaction type not allow
I searched the Forum and got some input.., but in that I have a clarification.
Please see my doubt and the forum input.
Internal Order as Investment Measure:
Can you explain me Step 10. Settle the amounts to Main Asset from AuC(Prcg type: Full) - KO88 once again.
How we can give the Receiver Main Asset master in KO88. In KO88 we can only provide the Internal Order. But that Internal Order is already settled to AuC in Step 8.
Please guide me.
Thanks.
Regards,
nms
Re: Settlement of cost center to final asset ?
Posted: Oct 27, 2009 11:40 AM
Hi,
Are you doing any settlement using the AUC asset ?
Normal practice is to Create an Auc Asset and settle cost to Auc. Once the asset is ready for use, finally settle the Auc to final asset.
This can be done in two ways like - line item settlement / investment measure.
Below are steps in two scenarios :
Internal Order as Investment Measure:
1. Define the AuC Asset Class (with investment measure) - OAOA
2. Define the Asset Class u2013 for Main Asset - OAOA
3. Define Investment Profile - OITA
a. Assign the AuC Asset Class (Step-1) in the investment profile
4. Assign Investment Profile to Model Order - OITA
5. Define Order Type (Investment) - KOT2
a. Settlement Profile - OKO7
b. Maintain Allocation Structures - OKO6
c. Planning Profile - OKOS
d. Budget Profile - OKOB
6. Create an Internal Order - KO01
a. With the Investment Profile (Step-2)
b. AuC automatically created by the system using Asset Class given in the Investment Profile
7. Post the amounts to IO - FB01
8. Settle the amounts to AuC from IO (Prcg type: Automatic) - KO88
9. Create the Main Asset - AS01
10. Settle the amounts to Main Asset from AuC(Prcg type: Full) - KO88
AuC using Line Item Settlement:
1. Define the AuC Asset Class (with Line Item Settlement) - OAOA
2. Define the Asset Class u2013 for Main Asset - OAOA
3. Define Order Type (Overhead) - KOT2
4. Create an AuC-Asset (using Step-1 Asset Class) - AS01
5. Create an Internal Order - KO01
a. Assign the AuC u2013 Asset in Settlement Rule in IO
6. Post the amounts to IO - FB01
7. Settle the amounts to AuC from IO - KO88
8. Create Main Asset (using Step-2 Asset Class) - AS01
9. Assign the Main Asset in IO (Step-5) - KO02
10. Settlement AuC u2013 Line Item List - AIAB
11. Settlement AuC - Receiver - AIBU
VVR

nms,
Your message is not very clear - while you have mentioned at what stage are you getting the above-mentioned error message, you haven't mentioned exactly what you were trying to do. The fact that you are getting this error is a straight-forward indication that you are attempting to do something that SAP does expect.
However, answering your query about how to use KO88, you have to settle the AuC to a FA (fixed asset, with asset class other than AuC ), as that will close the open AuC, transfer the value from the AuC to the FA and from this point onwards, all transactions will happen to this FA. Your statement "in KO88, we can only provide the Internal Order" is incorrect.
Hope this helps.
Regards
Gulshan

Error: "Transaction type could not be determined" during PO Creation fromSC

Hi all,
I'm working on SRM 5.5 with ECS.
During the creation of a PO I want to add a SC as an item of PO.
But when I chose the SC and click on the button Add to PO I recive the error:
Transaction type could not be determined
In the organizational unit I set the attribute BSA and DP_PROCT_TY.
there are other steps I have to do to join the transaction type of SC and PO?
rgs
enzo

Hi Enzo,
First check if the attribute BSA and DP_PROC_TY have the same value.
Then in the attribute value for BSA, change the source system for the document type to your SRM system.
Create a new PO and a shopping cart.
Try changing the PO by adding the shopping cart
Hopefully your problem may get resolved.
Thanks
Sanjeev

ABUMN: Posting with trans.type 300 not possible (No acquisition posted)

Hello everyone,
I have seen a few threads on this topic, however I am still not finding a resolution to my issue. I am very new to the FICO configuration scene and probably need a little more hand holding than the others who have asked this question.
I am having and issue using ABUMN while transfering a Capital Investment Project (CIP Asset) under a asset class of AUC, to a standard fixed asset. The CIP has been capitalized. However, when I try to perform the transfer I am receiving the following error:
Posting with trans.type 300 not possible (No acquisition posted)
Message no. AA324
Diagnosis
Transaction type 300 belongs to a transaction type group, which can only be used to post to assets to which posting has already been performed. However, no postings have been made to this asset.
Procedure
Use a transaction type from a transaction type group, which can be used for the first acquisition to an asset.
I have read through SAP NOTE 327088 (for retirements transfer variant 4) and it just doesn't help me with the issue. I know it probably should, but I do not know enough about this process in order for it to make a whole lot of sense.
If anyone can help me with this, it would be greatly appreciated. Again, I am very new, so I will probably have several follow-up questions as well.
Thanks in advance for the help!
Rhonda

Okay...
I have finally figured this out on my own.
When trying to transfer a capital investment project asset with an AuC class (asset under construction), ABUMN is not to be used.
1st. The internal order needs to be fully settled (KO02). Create a settlement rule "FUL" for the designated fixed asset.
2nd. Run "Actual Settlement" run via KO88.
This should transfer everything from the CIP asset to the fixed asset. You can double check this via the S_ALR_87011967 - ... by Plant report. Run this report prior to performing the steps above and the money will show in the CIP asset account, run it again after the above steps. The CIP should be zeroed out and the fixed asset should now carry the amount.

Transaction type 100 not possible (no affiliated company specified)

Hi Experts,
At the time of posting asset acquisition in F-90 I am getting following error
Transaction type 100 not possible (no affiliated company specified)
Message no. AA389
I checked transaction type 100 config. there, "Post to affiliated company" is selected
Awaiting your valuable reply.
Regards
Anand

Hi,
check SAPNET note 127650.
Best regards

Transaction type 180 not possible (no affiliated company specified)

Hi,
I am trying to do the down payment Request in F-47 with Purchase order and asset. When I am trying to do this by giving the Asset number and Purchase order with Item 10. I am getting this error Transaction type 180 not possible (no affiliated company specified). The vendor is also not linked to trading partner and not an affilated company specific.
Please help me solving this issue.
Regards,
Raj

Hi Raj,
If in OBY6, no company ID is defined for company codes, they are NOT affiliated companies and the opposite.
Please check also via OBA7 (document type), if the field "Enter trading partner" is flagged
If yes -> you need to use a transaction type (AO74) which post to affiliatedcompany
If no -> you need to use a transaction type which does NOT post to affiliated
Best regards Bernhard

Transaction type does not exist

While creating PR & PO for the Assets I am getting Following Error
Transaction type does not exist
Message no. AA_BAS_CUS_READ008
Diagnosis
The transaction type entered does not exist.
System Response
Processing is terminated.
Procedure
Check your entry.
Can any body please help me to make PR & PO.
Amit

Hello Amit,
Please verify also the APC account you have set in the account determination of the relevant asset class (the one to which belongs the asset in the PO).
Then kindly check the field status group assigned to this account in FS00.
Please make sure that the fields for asset main and subnumber are enable in the field status group definition and not suppressed.
In other customers this was the reason for such an error.
This should resolve your problem.
Best Regards,
Vanessa.

Error message is 'TYPE' is not a component of data object 'PAYLOAD'.

Hello,
I have sceanrio where file->Synchronus bapi ->File.
For this I have defined a bpm.
Text file inut will be read and converted using sender FCC.
Bpm will call a synchronus bapi from r/3 and collect response. I need to create a success or error response file from the status of bapi response. I have used switch step to do that.
But here when I give condtion as this XPath SOResonse./p1:Z_BAPI_SALESORDER_CREATEFROM3.Response/RETURN1/TYPE = S, SXI_CACHE gives status of bpm as 99 and error message is 'TYPE' is not a component of data object 'PAYLOAD'.
At the same time if i just put a condition of simple type container variable (SuccessCounter = 0), it gives status 0 in SXI_CACHE.
Pl can anyone suggest on this as its urgent.
thanks in advance,
Sharada

Thanks for quick response.
Yes BAPI response has TYPE field.
Pl cehck this response xml
<?xml version="1.0" encoding="UTF-8" ?>
- <rfc:Z_BAPI_SALESORDER_CREATEFROM3.Response xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
- <RETURN1>
<TYPE>E</TYPE>
<ID>V4</ID>
<NUMBER>115</NUMBER>
<MESSAGE>Purchase order number in document number: 304928 already exists</MESSAGE>
<LOG_NO />
<LOG_MSG_NO>000000</LOG_MSG_NO>
<MESSAGE_V1>304928</MESSAGE_V1>
<MESSAGE_V2 />
<MESSAGE_V3 />
<MESSAGE_V4 />
<PARAMETER>SALES_HEADER_IN</PARAMETER>
<ROW>0</ROW>
<FIELD />
<SYSTEM>DEV200</SYSTEM>
</RETURN1>
<SALESDOCUMENT />
- <EXTENSIONIN>
- <item>
<STRUCTURE>BAPE_VBAK</STRUCTURE>
<VALUEPART1>X</VALUEPART1>
<VALUEPART2 />
<VALUEPART3 />
<VALUEPART4 />
</item>
</EXTENSIONIN>
<ORDER_CCARD />
<ORDER_CFGS_BLOB />
<ORDER_CFGS_INST />
<ORDER_CFGS_PART_OF />
<ORDER_CFGS_REF />
<ORDER_CFGS_REFINST />
<ORDER_CFGS_VALUE />
<ORDER_CFGS_VK />
<ORDER_CONDITIONS_IN />
<ORDER_CONDITIONS_INX />
<ORDER_ITEMS_IN />
<ORDER_ITEMS_INX />
- <ORDER_KEYS>
- <item>
<REFOBJTYP />
<REFOBJECT>HEADER</REFOBJECT>
<REFOBJKEY />
<REFLOGSYS />
<DOC_NUMBER />
<ITM_NUMBER>000000</ITM_NUMBER>
<SCHED_LIN>0000</SCHED_LIN>
<COND_NO />
<CONDITEMNO>000000</CONDITEMNO>
<COND_ST_NO>000</COND_ST_NO>
<COND_COUNT>00</COND_COUNT>
<COND_TYPE />
<STATUS />
<TINDEX>000000</TINDEX>
<ADDRESS />
<ABRLI>0000</ABRLI>
<ABART />
</item>
- <item>
<REFOBJTYP />
<REFOBJECT>ADDRESS</REFOBJECT>
<REFOBJKEY />
<REFLOGSYS />
<DOC_NUMBER />
<ITM_NUMBER>000000</ITM_NUMBER>
<SCHED_LIN>0000</SCHED_LIN>
<COND_NO />
<CONDITEMNO>000000</CONDITEMNO>
<COND_ST_NO>000</COND_ST_NO>
<COND_COUNT>00</COND_COUNT>
<COND_TYPE />
<STATUS />
<TINDEX>000001</TINDEX>
<ADDRESS />
<ABRLI>0000</ABRLI>
<ABART />
</item>
- <item>
<REFOBJTYP />
<REFOBJECT>ADDRESS</REFOBJECT>
<REFOBJKEY />
<REFLOGSYS />
<DOC_NUMBER />
<ITM_NUMBER>000000</ITM_NUMBER>
<SCHED_LIN>0000</SCHED_LIN>
<COND_NO />
<CONDITEMNO>000000</CONDITEMNO>
<COND_ST_NO>000</COND_ST_NO>
<COND_COUNT>00</COND_COUNT>
<COND_TYPE />
<STATUS />
<TINDEX>000002</TINDEX>
<ADDRESS />
<ABRLI>0000</ABRLI>
<ABART />
</item>
- <item>
<REFOBJTYP />
<REFOBJECT>ADDRESS</REFOBJECT>
<REFOBJKEY />
<REFLOGSYS />
<DOC_NUMBER />
<ITM_NUMBER>000000</ITM_NUMBER>
<SCHED_LIN>0000</SCHED_LIN>
<COND_NO />
<CONDITEMNO>000000</CONDITEMNO>
<COND_ST_NO>000</COND_ST_NO>
<COND_COUNT>00</COND_COUNT>
<COND_TYPE />
<STATUS />
<TINDEX>000003</TINDEX>
<ADDRESS />
<ABRLI>0000</ABRLI>
<ABART />
</item>
- <item>
<REFOBJTYP />
<REFOBJECT>ADDRESS</REFOBJECT>
<REFOBJKEY />
<REFLOGSYS />
<DOC_NUMBER />
<ITM_NUMBER>000000</ITM_NUMBER>
<SCHED_LIN>0000</SCHED_LIN>
<COND_NO />
<CONDITEMNO>000000</CONDITEMNO>
<COND_ST_NO>000</COND_ST_NO>
<COND_COUNT>00</COND_COUNT>
<COND_TYPE />
<STATUS />
<TINDEX>000004</TINDEX>
<ADDRESS />
<ABRLI>0000</ABRLI>
<ABART />
</item>
</ORDER_KEYS>
- <ORDER_PARTNERS>
- <item>
<PARTN_ROLE>RE</PARTN_ROLE>
<PARTN_NUMB>LS-RETAIL</PARTN_NUMB>
<ITM_NUMBER>000000</ITM_NUMBER>
<TITLE />
<NAME />
<NAME_2 />
<NAME_3 />
<NAME_4 />
<STREET />
<COUNTRY />
<COUNTR_ISO />
<POSTL_CODE />
<POBX_PCD />
<POBX_CTY />
<CITY />
<DISTRICT />
<REGION />
<PO_BOX />
<TELEPHONE />
<TELEPHONE2 />
<TELEBOX />
<FAX_NUMBER />
<TELETEX_NO />
<TELEX_NO />
<LANGU />
<LANGU_ISO />
<UNLOAD_PT />
<TRANSPZONE />
<TAXJURCODE />
<ADDRESS />
<PRIV_ADDR />
<ADDR_TYPE />
<ADDR_ORIG />
<ADDR_LINK>0001</ADDR_LINK>
<REFOBJTYPE />
<REFOBJKEY />
<REFLOGSYS />
</item>
- <item>
<PARTN_ROLE>WE</PARTN_ROLE>
<PARTN_NUMB>LS-RETAIL</PARTN_NUMB>
<ITM_NUMBER>000000</ITM_NUMBER>
<TITLE />
<NAME />
<NAME_2 />
<NAME_3 />
<NAME_4 />
<STREET />
<COUNTRY />
<COUNTR_ISO />
<POSTL_CODE />
<POBX_PCD />
<POBX_CTY />
<CITY />
<DISTRICT />
<REGION />
<PO_BOX />
<TELEPHONE />
<TELEPHONE2 />
<TELEBOX />
<FAX_NUMBER />
<TELETEX_NO />
<TELEX_NO />
<LANGU />
<LANGU_ISO />
<UNLOAD_PT />
<TRANSPZONE />
<TAXJURCODE />
<ADDRESS />
<PRIV_ADDR />
<ADDR_TYPE />
<ADDR_ORIG />
<ADDR_LINK>0002</ADDR_LINK>
<REFOBJTYPE />
<REFOBJKEY />
<REFLOGSYS />
</item>
- <item>
<PARTN_ROLE>Z1</PARTN_ROLE>
<PARTN_NUMB>LS-RETAIL</PARTN_NUMB>
<ITM_NUMBER>000000</ITM_NUMBER>
<TITLE />
<NAME />
<NAME_2 />
<NAME_3 />
<NAME_4 />
<STREET />
<COUNTRY />
<COUNTR_ISO />
<POSTL_CODE />
<POBX_PCD />
<POBX_CTY />
<CITY />
<DISTRICT />
<REGION />
<PO_BOX />
<TELEPHONE />
<TELEPHONE2 />
<TELEBOX />
<FAX_NUMBER />
<TELETEX_NO />
<TELEX_NO />
<LANGU />
<LANGU_ISO />
<UNLOAD_PT />
<TRANSPZONE />
<TAXJURCODE />
<ADDRESS />
<PRIV_ADDR />
<ADDR_TYPE />
<ADDR_ORIG />
<ADDR_LINK>0003</ADDR_LINK>
<REFOBJTYPE />
<REFOBJKEY />
<REFLOGSYS />
</item>
- <item>
<PARTN_ROLE>AG</PARTN_ROLE>
<PARTN_NUMB>LS-RETAIL</PARTN_NUMB>
<ITM_NUMBER>000000</ITM_NUMBER>
<TITLE />
<NAME />
<NAME_2 />
<NAME_3 />
<NAME_4 />
<STREET />
<COUNTRY />
<COUNTR_ISO />
<POSTL_CODE />
<POBX_PCD />
<POBX_CTY />
<CITY />
<DISTRICT />
<REGION />
<PO_BOX />
<TELEPHONE />
<TELEPHONE2 />
<TELEBOX />
<FAX_NUMBER />
<TELETEX_NO />
<TELEX_NO />
<LANGU />
<LANGU_ISO />
<UNLOAD_PT />
<TRANSPZONE />
<TAXJURCODE />
<ADDRESS />
<PRIV_ADDR />
<ADDR_TYPE />
<ADDR_ORIG />
<ADDR_LINK />
<REFOBJTYPE />
<REFOBJKEY />
<REFLOGSYS />
</item>
</ORDER_PARTNERS>
<ORDER_SCHEDULES_IN />
<ORDER_SCHEDULES_INX />
- <ORDER_TEXT>
- <item>
<DOC_NUMBER />
<ITM_NUMBER>000020</ITM_NUMBER>
<TEXT_ID>Z001</TEXT_ID>
<LANGU>E</LANGU>
<LANGU_ISO />
<FORMAT_COL />
<TEXT_LINE />
<FUNCTION />
</item>
- <item>
<DOC_NUMBER />
<ITM_NUMBER>000030</ITM_NUMBER>
<TEXT_ID>Z001</TEXT_ID>
<LANGU>E</LANGU>
<LANGU_ISO />
<FORMAT_COL />
<TEXT_LINE />
<FUNCTION />
</item>
- <item>
<DOC_NUMBER />
<ITM_NUMBER>000040</ITM_NUMBER>
<TEXT_ID>Z001</TEXT_ID>
<LANGU>E</LANGU>
<LANGU_ISO />
<FORMAT_COL />
<TEXT_LINE />
<FUNCTION />
</item>
- <item>
<DOC_NUMBER />
<ITM_NUMBER>000050</ITM_NUMBER>
<TEXT_ID>Z001</TEXT_ID>
<LANGU>E</LANGU>
<LANGU_ISO />
<FORMAT_COL />
<TEXT_LINE />
<FUNCTION />
</item>
- <item>
<DOC_NUMBER />
<ITM_NUMBER>000020</ITM_NUMBER>
<TEXT_ID>Z001</TEXT_ID>
<LANGU>E</LANGU>
<LANGU_ISO />
<FORMAT_COL />
<TEXT_LINE />
<FUNCTION />
</item>
- <item>
<DOC_NUMBER />
<ITM_NUMBER>000030</ITM_NUMBER>
<TEXT_ID>Z001</TEXT_ID>
<LANGU>E</LANGU>
<LANGU_ISO />
<FORMAT_COL />
<TEXT_LINE />
<FUNCTION />
</item>
- <item>
<DOC_NUMBER />
<ITM_NUMBER>000040</ITM_NUMBER>
<TEXT_ID>Z001</TEXT_ID>
<LANGU>E</LANGU>
<LANGU_ISO />
<FORMAT_COL />
<TEXT_LINE />
<FUNCTION />
</item>
- <item>
<DOC_NUMBER />
<ITM_NUMBER>000050</ITM_NUMBER>
<TEXT_ID>Z001</TEXT_ID>
<LANGU>E</LANGU>
<LANGU_ISO />
<FORMAT_COL />
<TEXT_LINE />
<FUNCTION />
</item>
</ORDER_TEXT>
- <PARTNERADDRESSES>
- <item>
<ADDR_NO>0001</ADDR_NO>
<FORMOFADDR />
<NAME />
<NAME_2 />
<NAME_3 />
<NAME_4 />
<C_O_NAME />
<CITY />
<DISTRICT />
<CITY_NO />
<POSTL_COD1 />
<POSTL_COD2 />
<POSTL_COD3 />
<PO_BOX />
<PO_BOX_CIT />
<DELIV_DIS />
<STREET />
<STREET_NO />
<STR_ABBR />
<HOUSE_NO />
<STR_SUPPL1 />
<STR_SUPPL2 />
<LOCATION />
<BUILDING />
<FLOOR />
<ROOM_NO />
<COUNTRY />
<LANGU />
<REGION />
<SORT1 />
<SORT2 />
<TIME_ZONE />
<TAXJURCODE />
<ADR_NOTES />
<COMM_TYPE />
<TEL1_NUMBR />
<TEL1_EXT />
<FAX_NUMBER />
<FAX_EXTENS />
<STREET_LNG />
<DISTRCT_NO />
<CHCKSTATUS />
<PBOXCIT_NO />
<TRANSPZONE />
<HOUSE_NO2 />
<E_MAIL />
<STR_SUPPL3 />
<TITLE />
<COUNTRYISO />
<LANGU_ISO />
<BUILD_LONG />
<REGIOGROUP />
<HOME_CITY />
<HOMECITYNO />
<PCODE1_EXT />
<PCODE2_EXT />
<PCODE3_EXT />
<PO_W_O_NO />
<PO_BOX_REG />
<POBOX_CTRY />
<PO_CTRYISO />
<HOMEPAGE />
<DONT_USE_S />
<DONT_USE_P />
<HOUSE_NO3 />
<LANGU_CR />
<LANGUCRISO />
</item>
- <item>
<ADDR_NO>0002</ADDR_NO>
<FORMOFADDR />
<NAME>SUPERIOR SELECTED STONE</NAME>
<NAME_2 />
<NAME_3>33-53 10TH STREET</NAME_3>
<NAME_4 />
<C_O_NAME />
<CITY />
<DISTRICT />
<CITY_NO />
<POSTL_COD1 />
<POSTL_COD2 />
<POSTL_COD3 />
<PO_BOX />
<PO_BOX_CIT />
<DELIV_DIS />
<STREET />
<STREET_NO />
<STR_ABBR />
<HOUSE_NO />
<STR_SUPPL1 />
<STR_SUPPL2 />
<LOCATION />
<BUILDING />
<FLOOR />
<ROOM_NO />
<COUNTRY />
<LANGU />
<REGION />
<SORT1 />
<SORT2 />
<TIME_ZONE />
<TAXJURCODE />
<ADR_NOTES />
<COMM_TYPE />
<TEL1_NUMBR />
<TEL1_EXT />
<FAX_NUMBER />
<FAX_EXTENS />
<STREET_LNG />
<DISTRCT_NO />
<CHCKSTATUS />
<PBOXCIT_NO />
<TRANSPZONE />
<HOUSE_NO2 />
<E_MAIL />
<STR_SUPPL3 />
<TITLE />
<COUNTRYISO />
<LANGU_ISO />
<BUILD_LONG />
<REGIOGROUP />
<HOME_CITY />
<HOMECITYNO />
<PCODE1_EXT />
<PCODE2_EXT />
<PCODE3_EXT />
<PO_W_O_NO />
<PO_BOX_REG />
<POBOX_CTRY />
<PO_CTRYISO />
<HOMEPAGE />
<DONT_USE_S />
<DONT_USE_P />
<HOUSE_NO3 />
<LANGU_CR />
<LANGUCRISO />
</item>
- <item>
<ADDR_NO>0003</ADDR_NO>
<FORMOFADDR />
<NAME>Langenscheidt Publishers Inc.</NAME>
<NAME_2 />
<NAME_3 />
<NAME_4 />
<C_O_NAME />
<CITY />
<DISTRICT />
<CITY_NO />
<POSTL_COD1 />
<POSTL_COD2 />
<POSTL_COD3 />
<PO_BOX />
<PO_BOX_CIT />
<DELIV_DIS />
<STREET />
<STREET_NO />
<STR_ABBR />
<HOUSE_NO />
<STR_SUPPL1 />
<STR_SUPPL2 />
<LOCATION />
<BUILDING />
<FLOOR />
<ROOM_NO />
<COUNTRY />
<LANGU />
<REGION />
<SORT1 />
<SORT2 />
<TIME_ZONE />
<TAXJURCODE />
<ADR_NOTES />
<COMM_TYPE />
<TEL1_NUMBR />
<TEL1_EXT />
<FAX_NUMBER />
<FAX_EXTENS />
<STREET_LNG />
<DISTRCT_NO />
<CHCKSTATUS />
<PBOXCIT_NO />
<TRANSPZONE />
<HOUSE_NO2 />
<E_MAIL />
<STR_SUPPL3 />
<TITLE />
<COUNTRYISO />
<LANGU_ISO />
<BUILD_LONG />
<REGIOGROUP />
<HOME_CITY />
<HOMECITYNO />
<PCODE1_EXT />
<PCODE2_EXT />
<PCODE3_EXT />
<PO_W_O_NO />
<PO_BOX_REG />
<POBOX_CTRY />
<PO_CTRYISO />
<HOMEPAGE />
<DONT_USE_S />
<DONT_USE_P />
<HOUSE_NO3 />
<LANGU_CR />
<LANGUCRISO />
</item>
</PARTNERADDRESSES>
- <RETURN>
- <item>
<TYPE>E</TYPE>
<ID>V4</ID>
<NUMBER>115</NUMBER>
<MESSAGE>Purchase order number in document number: 304928 already exists</MESSAGE>
<LOG_NO />
<LOG_MSG_NO>000000</LOG_MSG_NO>
<MESSAGE_V1>304928</MESSAGE_V1>
<MESSAGE_V2 />
<MESSAGE_V3 />
<MESSAGE_V4 />
<PARAMETER>SALES_HEADER_IN</PARAMETER>
<ROW>0</ROW>
<FIELD />
<SYSTEM>DEV200</SYSTEM>
</item>
- <item>
<TYPE>E</TYPE>
<ID>V4</ID>
<NUMBER>219</NUMBER>
<MESSAGE>Sales document was not changed</MESSAGE>
<LOG_NO />
<LOG_MSG_NO>000000</LOG_MSG_NO>
<MESSAGE_V1 />
<MESSAGE_V2 />
<MESSAGE_V3 />
<MESSAGE_V4 />
<PARAMETER />
<ROW>0</ROW>
<FIELD />
<SYSTEM>DEV200</SYSTEM>
</item>
</RETURN>
</rfc:Z_BAPI_SALESORDER_CREATEFROM3.Response>

ABUMN Intracompnay asset transfer error AA389 Transaction type 300 not pos

Similar Messages

Maybe you are looking for