Idoc Message Type FIDCC2 Not Posting CO Documents

Hi Everyone,
Our company is just about to begin using message type FIDCC2 to post entries through FB60/FB65 and FB50. When you manually enter an entry through any of these transactions, an FI, CCA and PCA document are all created simultaneously. However, when posting an identical entry through message type FIDCC2, only an FI document is created. Why are the other documents not being created and is there something that I am missing from configuration or some sort of trigger that is supposed to create the other entries? Please assist as this is extremely urgent.
Thanks to all that can assist,
Pete

Hi Peter,
Is your company uses any of the profitability segment fields as well? If so how are you updating this information on to the FIDCC2 idoc and how are you generating any COPA document simultaneously. I am in the same situation and my FIDCC2 idoc updates the FI, CO, PCA components but not the COPA. I am not sure where to populae the Profitability segments on the FIDCC2 type. Please share if you have same issues in your company.
Regards
Elphick

Similar Messages

URGENT! Idoc Message Type FIDCC2 Not Posting CO Documents

Hi Everyone,
Our company is just about to begin using message type FIDCC2 to post entries through FB60/FB65 and FB50. When you manually enter an entry through any of these transactions, an FI, CCA and PCA document are all created simultaneously. However, when posting an identical entry through message type FIDCC2, only an FI document is created. Why are the other documents not being created and is there something that I am missing from configuration or some sort of trigger that is supposed to create the other entries? Please assist as this is extremely urgent.
Thanks to all that can assist,
Pete

Hi Peter,
Is your company uses any of the profitability segment fields as well? If so how are you updating this information on to the FIDCC2 idoc and how are you generating any COPA document simultaneously. I am in the same situation and my FIDCC2 idoc updates the FI, CO, PCA components but not the COPA. I am not sure where to populae the Profitability segments on the FIDCC2 type. Please share if you have same issues in your company.
Regards
Elphick

IDOC message type LOIPLO not triggering

Hi Friends
Our client want to send firmed planned orders to External system through outbound IDOC LOIPLO
So we are using MF50 to firm the planned orders.
The idoc message type LOIPLO is not triggering.
How to trigger IDOC message type LOIPLO . What are the settings we have to do.
Regards,
Srihari.M

dear friend,
Message Type : LOIPLO
Basic Type : LOIPLO01
You need not create any custom IDOC type as we are having a standard IDOC type available within SAP, but you need to write a custom function module to read the data from the IDOC segments and then call the below BAPI to post the Planned Order.
Check the input parameters of BAPI and gothrough the documentation of the Basic Type in WE60 transactions, whether all the necessary input parameters of the BAPI are covered in the standard IDOC type, if not then we need to customize the standard basic type to meet the requirements.
Bapi which needs to be used is BAPI_PLANNEDORDER_CREATE
good luck!

IDOC message type WMMBXY not including Serial numbers in GR material documents when created with reference to an Inbound delivery

Hello,
We currently have an inbound ALE process (message type WMMBXY and basic type WMMBID02) to post GR's against inbound delivery. If the inbound delivery item is maintained with serial numbers, we want those serial numbers to be pulled into the goods movement material document (and stored in SER03).
Currently segment E1MBXYJ is maintained with the inbound delivery number in field VLIEF_AVIS and Inbound delivery item number in field
VBELP_AVIS. In segment E1MBXYI, no purchase order is assigned and the fields EBELN and EBELP are blank. The movement indicator (KZBEW) has the value 'B'.
Even after making the above settings, the serial number(s) maintained on the Inbound delivery item do not get saved to the material document.I did look at OSS note 833603 (Solution for 2 - GR for Inbound delivery) and we have followed the same settings. This works when there is no serial number in the Inbound delivery. However if we have serial numbers, the IDOC posts successfully, however the material documents in MB03 do not have any serial numbers copied over from the Inbound delivery where the serial numbers are definitely assigned.
Any help you can provide is greatly appreciated!
Thanks,
Ashvin
P.S
If we manually create the GR via MIGO, the serial numbers are automatically applied to the GR material document. This is what we want to accomplish via the above IDoc process.

Hi
Try with enhancement MWMIDO08. See note 833603 - EDI: Goods receipt for stock transport order for further information.
I hope this helps you
Regards
Eduardo

Message type :FIDCC2/ IDOCFIDCCP02 - Triggering outbound IDOC

I have to send the FI accounting document of certain customer groups to the third party system .
Can anyone pls let me know how to trigger the outbound IDOC for the message type FIDCC2 after the FI document is created.
I have configured BD64 but can not find which program to trigger to generate the outbound IDOC with the FI data.
Thanks,
Prashanth

Hi Anji,
Thanks for the Reply. But i think ORDRSP is for Order Confirmations.
But I have to send Outbound Idoc for a Schedule Agreement.
Whether the same Idoc type & Messge type used for SO/PO(e.g ORDERS05, ORDERS/ORDCHG) can be used for Scheduling Agreement.
Please Advice.
Regards,
Anbalagan

IDOC Message Type FIDCCP02 - Error RW029

Hi All,
We are trying to post a FB01 using a IDOC message type - FIDCC2 and struck at error message -
<b>Accounting transaction not permitted for posting in FI/CO
Message no. RW029</b>
When i try to post directly using the exact data in the IDOC, through FB01, there is no problem.
Debug showed that the error is in the following -
Include <b>LRWCLF01</b>
check business process
SELECT SINGLE * FROM t022 INTO ld_t022
WHERE activity = t_acchd-glvor.
IF sy-subrc IS INITIAL.
IF LD_T022-VORGTYP = 0 OR <---------
IF ld_t022-satztyp <> 0.
MESSAGE e029 WITH t_acchd-glvor.
ENDIF.
ELSE.
MESSAGE e029 WITH t_acchd-glvor.
ENDIF.
If this is not the right message type to use, can you suggest any other message type? FB01 we are trying to post is a simple GL posting, no tax, no withholding, etc. IDOC is just a 2 line posting.
Any help/advice is highly appreciated.
Many Thanks,
Shashi

Hi Shashi ,
This table is for Business Process t022 based on activity .
Check your customise settings .
There is no problem with message type .
Please reward if useful

MB1B transfer posting Idoc/Message type for outbound and inbound

Hello All
Can anyone tell me the idoc/message type for movement type 313 outbound and 315 inbound to SAP. This is for MB1B Enter Transfer Positing.
Thanks
Ricky

Its WMMBXY

Docu of Idoc message type CRMXIF_ORDER_SAVE_M02 for service request

Hi,
We are using the customer interaction center / service desk in CRM 7.0 and want to send service calls from other systems to our CRM service desk.
I've found that this should be possible via IDOC CRMXIF_ORDER_SAVE_M02.
Does someone has more documentation of this idoc message type (meaning of the fields, obligatory fields, ...) ?
Thank you,
Stefan

Hi,
Go to we19 t-code, there give messgae type CRMXIF_ORDER_SAVE_M and then execute.
Next screein beside EEIDC double click and give send and receiver port.
After that clcck CRMXIF_BUSTRANS popup will open. Fill required fields.
Then expand CRMXIF_BUSTRANSA do the same for all.
After that click start oubound processing.
For more information go to SPRO->CRM->CRM middleware and related componets->exchange data with external components->XIF adapters then click OVERVIEW documentation help. Then click CRMXIF_ORDER_SAVE.
You will get the information on outbond as well as inobound.
Regards
Srinu
Edited by: sreenivasulareddy eragamreddy on Jul 10, 2009 7:45 PM

IDOC Message type for FB01 transaction.

Hi,
I am going to get a file which I will pass through PI (XI) and bring into IDOC and post into SAP ECC 6.0.
I just wanted to know which IDOC message type / basic type I should use for posting an FI document i.e. FB01 transaction.
Rgds

Hi,
please read SAP notes 892103 and 551035.
The correct IDOC type should be FIDCC1 / FIDCC2.
Best regards,
Andreas

ALE Distribution for Message Type FIDCC2

Dear all,
I would like to confirm my steps below in setting up the ALE distribution of message type FIDCC2, to ensure that I did not do anyhting that impact other company code that already live in the system :-
1. Use tcode OB87 to add the Global Company Code, XBJ01.
2. Use tcode OBV7 to link a dummy (non-existence in sending system)
Chart of Account to the Global Company code XBJ01.
3. Use tcode OBB5 to assign the Global Company Code, XBJ01, setup in step 1. to the an existing company code BJ01.
4. Use tcode BD64 to setup a distribution with message type FIDCC2, and
filter with value XBJ01.
5. Create an FI document using tcode FB01 with company code BJ01.
6. IDOC is created successfully with message type FIDCC2.
Is there above steps correct? As there are times I receive an error message when trying to do a PGI with company code other than BJ01 "F1302 No cross-system company code is defined for company code TR01".
Another question is, with setting up of FIDCC2 with ALE distribution, any transaction in SAP that will generate a FI document will have IDOC created, right?
Thank you.
Best Regards
Chee Hean

I don't know if you still have this problem but my team and I faced a similar issue in production. Due to a project we're handling, a tool that we are executing requested us to create a Distribution Model based on FIDCC2. This stuck hundreds of thousands of FI Document. Actually, for any FI document the system generated an FIDCC2 and it's not possible to reuse those IDocs because the FIDCC2 Message Type has a structure completely different from FIDCMT (the original message that the system should generate). We identified all the IDoc that should be generated and re-create the Idocs in the target system and the Idocs we posted correctly. We change the FIDCC2 IDocs status to 62 or 32 (depending if inbound system or outbound system). I recommend to investigate about this message type before use it. This Message Type is stronger than any other message type so it must be filter perfectly otherwise, for sure, problems will appear.
Regards,
Hugo

How to recreate Idoc - message type FIDCC1

Hi Experts,
We have configured sending IDoc using ALE during execution of Tcode FPG1 with message type FIDCC1- Send entire FI documents (user exit 003/4) and basic type FIDCCP01
We are facing issues sometimes, the financial entry is posted but the IDoc is not created for the same. Is there any way we can regenerate the IDoc ?
Any suggestion will be of great help.
Thanks & Regards
Satyajeet

HI,
You can use WE19 but make sure you test this in TEST client.
This is quickfix solution and shall not be use regularly.
Regards,
Paresh

FIDCCP01 Message type FIDCC2

Hello,
I am trying to use message type FIDCCP to create idocs for FI Document posting. However i am unable to see any idocs created. I have configured the system and activated change pointers for FI Documents. My question is does anybody have previous experience with FIDCCP message and change pointers and are idocs created using change pointers for FIDCC2. As when i run rbdmidoc and when i try to give FIDCC2 it says "message type fidcc2 cannot be sent via change pointers. Request you to help in this regards.
Regards,
Shekhar Kulkarni

Hello Shekhar,
you don't need change-pointers.
You must customize the ALE-Scenarion for FIDCC
Best Regards
Anton

IDOC message type for "Site" in SAP Retail module?

Hi All,
We have the need to transfer master data (through master data change pointers) of Retail Sites within the SAP Retail module (transaction: WB01, WB02). Does anyone know if there's an IDOC message/type already associated with this? Thanks in advance for your help!
Cheers,
Matt

Hi,
please read SAP notes 892103 and 551035.
The correct IDOC type should be FIDCC1 / FIDCC2.
Best regards,
Andreas

Inbound IDOC for sales orders not posting the configuration data

Hi all,
I am facing a problem in posting the inbound IDOC (message type ORDERS). The configuration data maintained in the parent segment E1CUCFG and in the segment E1CUVAL is not getting posted though i am passing the data in these segments which is 100% correct.
Can any one solve this problem

Hi Ravi,
Please check the two segments are active. You can do that in BD53.
In BD53 enter message type, and make the segments active.
If segments are active, it appears in white colour.
After this post the IDoc and check with segments.
If its useful, award points pls..
Regards,
Bharadwaj

Contract creation in Backend with Idoc message type BLAORD

Hello,
We are creating Backend contracts from the Bidding engine functionality. We only want to create backend contracts and did the necesary configuration.
We activated BADI: BBP_DETERMINE_LOGSYS
Method CONTRACT_LOGSYS_DETERMINE.
We did not yet implement BADI:
BBP_CTR_BE_CREATE in SRM 5.0
In SAP R/3 Backend system (Version 46C) we see SAP is trying to create a contract via Idoc message Type: BLAORD.
In the trx BD87 in the backend we get status 51 :
Mesage number: 00 055
"Make an entry in all required fields"
In the segments of the Idoc however we do not see which field is missing!
How can we best analise this problem. Or maybe anyone can give us a a hint what is missing.
Thanks for any reply.
Aart

Hello RRK,
In ref. to your mentioning to change the backend configuration from WKK to MKK might not be as easy to do for organizations. As those configurations effect the overall creation of purchasing document types in R/3.
The Key issue is why the "Target Value" in the Header of the SRM GOA does not get transferred to the R/3 contract. That's why the issue is still there.
Were you guys able to figure out why that was missing? In the BLAORD IDoc the Target Value seems to not get transferred from SRM - its 0.00 if the IDoc is reviewed in WE19. This seems to be the problem.
Just wanted to know if you see the same issue in ur system.
Thanks.
Sunny.

Idoc Message Type FIDCC2 Not Posting CO Documents

Similar Messages

Maybe you are looking for