IDOC FIDCC1/FIDCCP02 - Error RW029

I am trying to post an FI document using IDoc 'FIDCC1/FIDCCP02 ' and get error 'Accounting transaction not permitted in FI/CO (RW029)'. Anyone know what this may mean?

Hi,
In include LRWCLF01 check this part of the code where the error occurs:
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.
regards
Aveek

Similar Messages

IDOC FIDCC1/FIDCCP02 Issue

Here is the scenario :
System A is sending IDOC to System B and I am posting an FI document using IDoc 'FIDCC2/FIDCCP02 '.
How can we transfer IDOC PROCESSED information back to System A. In other workds how can we send an
ACKNOWLEDGEMENT message to System B ?
Thanks, Mel

Hi,
Using the Z Program you can get done this requirement. Create a Z Program and schedule it in the background, you can schedule this based on the frequency of that IDoc and in the same way how it is coming crete the outbound requirements and use the same Z Program in this case.
Table : EDIDC which gives you the status details of the IDoc.
Better have a discussion with ABAPer for more clarity.
VVR

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

IDoc FIDCC1/FIDCCP02 - Base line due date (ZFBDT)

When creating a FI posting using IDOC FIDCCP02, at the item level the 'terms of payment(ZTERM)' is not taken from the vendor master and the'Baseline date for due date calculation(ZFBDT)' is not calculated. When line item is entered manually in FB01, these fields are calculated. In config the 'baseline date' was configured to be 'posting date'. Any special config necessary when posting tru IDoc or is this a bug?

You can use the user exit to set the date in program LF050F00 (example: line 574). Search for user exits in the function module IDOC_INPUT_FIDCC1.

ALE: FI-IDoc FIDCCP01/FIDCCP02

Hi all,
i have a problem with creating and sending IDocs for FI-Documents. I use Message type FIDCC1 and the IDoc Basictype FIDCCP01 (with an extension). In the Partnerprofiles i maintained this data combination. But by posting an FI Document an IDoc with IDoc type FIDCCP02 is created but faulty with the reason of not existing entries in the outbound table. The reason of faulty is correct, but i do not really understand why an FIDCCP02 is created. I assume that the reason is the used function module 'FI_IDOC_CREATE_FIDCC1' (i think that is used) and the IDoc type that is used is hard coded FIDCCP02. But some created IDocs fit to my maintained partner profile (FIDCCP01 with extension). So that i am really confused and do not really know what has to be done now.
An OSS message (459938) says that the old FIDCCP01 still can be used. How?
I am working with a 46B (PatchLevel 51).
Please help.
Thanks in advance
Michael

Hi,
in WE20 you maintain the partner profile. Selecting a partner you see which messages are distributed (outbound and inbound). If you select a message type and show the details (for example Screen 'Partner profiles: Outbound parameters) you see in addition to the message type a field for message code (3 digits) and message function (3 digits). With these two additional informations you can separate processes using the same message type.
Think about several systems sending data with one message type to one central system and you want to handle the inbound different. Therefore you can use message codes and message functions.
My problem was that i didn't really know what i did when i used this the first time. We wanted to distribute the message FIDCC1 with the IDoc type FIDCCP01. We have done several times with other systems and it always runs without any problems. But when i started using MESCOD and/or MESFCT an error appears with IDoc type FIDCCP02 and that our additional segment is not identifyable).
So i had a look how the ALE service version conversion works. As i wrote before our Application creates a master IDoc with type FIDCCP02 and former this was converted to FIDCCP01.
It is done like following (sequences of calls):
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
PERFORM 'IDOC_SELECTION_AND_SERVICES'
CALL FUNCTION 'ALE_IDOC_SERVICES_APPLY_OUT'
PERFORM 'IDOC_CONVERT_VERSION_OUTBOUND'
PERFORM 'CHANGE_IDOC_VERSION'
The program takes the values of the IDoc control information (MSGTYP, MESCOD, MESFCT) and checks them against table EDP13. If an entry exists the change of the IDoc version will be done, else not.
So my fault was to maintain the partner profile with MESCOD and MESFCT but in the control information these values were empty (how should the application program know which walue have to be filled in?). So i did it in an exit (F050S004 FM EXIT_SAPLF050_007):
>>> Enrich IDoc Control structure with a value for the logical
message function, to make a difference for different processes in
the partner profile.
idoc_control-mesfct = c_mesfct_fidcc1. "YFA
Now it fits to my partner profile and it runs properly.
But don't forget to maintain the partner profile in the receiving system equal and VERY IMPORTANT think about the inbound processing. You have to maintain the Assignment of the inbound FM to log. Message and IDoc type with MESCOD and MESFCT using transaction WE57.
Thats all.
Hope it helps.
Michael

STPPOD Idoc creation status : Error in ALE Service

Experts,
I am trying to send GR from MM to SUS in MM-SUS Classic Scenario on ECC 6.0 Server. I have also configured Goods REceipt Notifications Functionality to sending GR from MM to SUS.
When i am trying to send GR Idoc is generated (STDPOD) but i am getting the Error whose status - 29 in WE02 t-code :
Status Message for Selected IDoc
Status Text:   IDoc: 0000000000211243 Status: Error in ALE service
T100 Text:     Entry in outbound table not found
While i have properly configured Partner Profile for Message Type STPPOD :
Partner Role          Basic Type     Receiver Port           Application     Output Mode
LS        DELVRY03      A000000018 (XI port)           GRN               Transfer Idoc Immediately
When i try WE19 t-code for this idoc, i found the error "Port '' does not exist in the table of port descriptions"
while i have already defined port (A000000018)in WE21 t-code and this port also working fine for other messages.
Please suggest.
Thanks.
Regards,
Pawan Keshwani

Nikhil,
Issue is resolved it was the wiered error. As i removed LS from the field Partner Role in STPPOD message at partner profile(WE20) for SUS Client in ECC. Now the message STPPOD outbound message working fine.
Thanks.
Regards,
Pawan Keshwani

IDOCs Packaging ... What if one IDOC is in error in the packet ?

Hi all,
What will happend to the rest of the IDOC in the packet ?
Lets say, i packaged my IDOC in a bunch of 5. The first 3 IDOCs, their payload are ok. However the 4th has a bad payload and it crash in the mapping section ...
Does the first 3 IDOC (and the 5th one) will be sent and the one in error (4th one) will remain (in XI for mapping error) ?
Thank.
michel osborne

Hi chandrakanth.k,
Thank for your response. I have seen these blogs. I am not using the BPM.
I am using the IDXPW + Messages filter (sxmsfilter) to packaged the IDOCs.
I have made some tests ... wird enough ...
test #1:
idoc (1) - error
idoc (2) - valid
idoc (3) - valid
.... etc ...
test #2:
idoc (1) - valid
idoc (2) - error
idoc (3) - valid
test #3:
idoc (1) valid
idoc (2) valid
idoc (3) - valid
idoc (4) - error
In the "test #1", idoc (2) & idoc (3) are processed correctly (idoc sent to the SAP ECC backend system). Idoc (1) is stuck in XI with errror (mapping) which is OK.
In the "test #2", work the same as in test #1, idoc(1) & idoc(3) hs been delivered to the SAP ECC backend system.
However, in the "test #3"all idoc (1, 2, 3,4) are stuck in XI ... idoc(4) in error (which is ok), idoc(1) up to - idoc(3) in sxmb_moni has the racing flag .... but not delivered to the SAP ECC backend system ... they have the status: Message Schedule for outbound side ....
It seem that each time the package end with and idoc in error, the entire batch get stuck in XI .
How can i get sent them (test case #3) !!?!?
Thank in advance !

IDOC Tables with Errors Post System Refresh

Hi Everyone,
Is there any Report or other way through which one can get List of IDOC Tables with Errors Post System Refresh.
Thanks,
Regards,
- Ishan

Hi,
While selecting the Infopackage to run the INIT load, it is taking me to the ECC login screen. Once i enter my credentials, its showing a dump with the message:
Short text of error message:
No RFC authorization for user XXXXX ( RSA8 ).
Long text of error message:
Technical information about the message:
Message class....... "RSAR"
Number.............. 051
Variable 1.......... "No RFC authorization for user XXXXX ( RSA8 )."
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
Please advice.
Regards
sneha

Exit after updating master data of IDOC type FIDCCP02 in inbound isde

Hi All,
I am using FI_IDOC_CREATE_FIDCC2 fm in outbound side to create master record data and
Fm IDOC_INPUT_FIDCC2 is used at inbound side to update the corresponding tables of IDOC type FIDCCP02?
Is the above process correctly update the tables related to idoc type FIDCCP02 at inbound side?
If so,Can anyone please tell me the exit or badi triggered after updating all the fields of IDOC type FIDCCP02 with the Fm IDOC_INPUT_FIDCC2?
Thank you,
Swetha. C

Hi All,
Can anyone please tell me the badi or exit triggered after the execution of fm IDOC_INPUT_FIDCC2 (used to post the IDOC type FIDDCP02)?
I want the BADI or exit that is triggered after posting all the data to corresponding tables of IDOC type FIDCCP02 with the Function module IDOC_INPUT_FIDCC2 in inbound side.
Thank You,
Swetha.C

Idoc or trfc error

Hi sap bw'iets
can any one describe step-by-step process to sloving IDOC or TRFC ERROR in production support.
thank you.
regards,
kiran

hi kiran,
sometimes idocs stucks in the source system, so it shows yellow in the monitor even if every thing else is showin green. so to correct this, go to environment -> Transact RFC -> In the Source System. If the status is showing "Executing" then leave it, otherwise u can drag it to BW by selecting execute LUW (F6), by selecting the tRFC.
hope this helps.
Regards,
Purvang
Assigning Point is to say Thanks in SDN *

Transfer(IDocs and TRFC) error when use infopackage to load data from R/3

I create an infopackage to load data from R/3, when start immediately ,there is no data transfered. The return error is :
transfer(IDocs and TRFC): Errors occurred
request IDoc: Application document not posted
Does anybody know how can correct this error?
Thanks great.

Hi Yimeng,
Check in SM58 transaction code in R/3 and see if any LUWs are stuck there. If so you can execute them manually and complete the data load.
regards,
Sumit

IDOC FIDCC1 - GL amount ignored depending on AWTYP

Hi,
We are sending the IDOC FIDCC1 to a new SAP GL system and we have problems when the FI document sent has different GL currency (PSWBT, PSWSL) than the document currency. In this case, only when we sent AWTYP = FKKSU, the GL amount is copied with the correct currency, otherwise it remains in the document currency ( it ignores what we send in the IDOC ).
These are two examples, the only difference in the idoc is the AWTYP. As you can see, the actual document created is different depending on the AWTYP. GL amount PSWBT is not correct for the first document, since we sent in the IDOC currency EUR.
IDOC 1 creates document 6000000005 see below
E1FIKPF -> AWTYP = BKPF
E1FISEG -> WRBTR = DMBTR = 1000 PLN
                   PSWBT = 50
                   PSWSL = EUR
IDOC 2creates document 6000000006 see below
E1FIKPF -> AWTYP = FKKSU
E1FISEG -> WRBTR = DMBTR = 1000 PLN
                   PSWBT = 50
                   PSWSL = EUR
documents created:
BKPF
BELNR      GJAHR AWTYP
6000000005 2010 BKPF
BSEG
BUZEI DMBTR            WRBTR            PSWBT            PSWSL
001          1.000,00         1.000,00         1.000,00 PLN
002          1.000,00         1.000,00         1.000,00 PLN
BKPF
BELNR      GJAHR AWTYP
6000000006 2010 FKKSU
BSEG
BUZEI DMBTR            WRBTR            PSWBT            PSWSL
001          1.000,00         1.000,00            50,00 EUR
002          1.000,00         1.000,00         1.000,00 PLN
We want GL amount in the correct currency, but we dont want to use AWTYP = FKKSU, since it belongs to another scenario... Has anyone faced a similar issue?
Thanks in advance!!
Aaron

Custom error in outbound idoc FIDCC1

Hi all,
I am generating outbounds idocs for FI documents and i need to put some of them in error. I need the FI Document created and the idoc in error so that i can reprocess it later. To do that i am using the User Exit EXIT_SAPLF050_007
Enhancement - F050S004 FIDCMT, FIDCC1, FIDCC2: Change outbound IDoc/do not send
""Lokale Schnittstelle:
*" IMPORTING
*" VALUE(MESSAGE_TYPE) LIKE EDMSG-MSGTYP
*" TABLES
*" IDOC_DATA STRUCTURE EDIDD
*" CHANGING
*" VALUE(IDOC_CONTROL) LIKE EDIDC STRUCTURE EDIDC
*" VALUE(DISTRIBUTION) LIKE BOOLE STRUCTURE BOOLE
*" OPTIONAL
IDOC_CONTROL-status = '26'.
The problem is that in the UserExit i set the Idoc Status to some value diferent than 3 (Data passed to port OK) but finally the idoc is created with the status 3.
Does anybody know how to change the idoc status in the creation from 3 to for example 26 or 27? ( an error idoc status ).
thanks!!

Hi,
In the partner profile, set the option as Collect IDOC's option.
Create a background job in which the first step of that should be your custom program and the second step is RSEOUT00 program.
In your custom program, validate the idoc if you feel your idoc is correct then leave it like that and if you feel there is some problem in the idoc then flag that error idoc for deletion that means that error idoc will not be sent to your partner.
For flagging an outbound idoc to deletion is nothing setting the idoc status to 31. This you can do with the program RC1_IDOC_SET_STATUS.
Thanks,
Mahesh.

JDBC - XI - IDOC scenario, SM58 error

I am trying to set up a scenario with JDBC -> XI-> IDOC. I seem to get the data, but when I look at it in SXMB_MONI, I get the checkered flag, for the overall status, but a red flag for the outbound status. This led me to SM58 where I see this error "No authorization to send IDocs with message type Z...". It shows the caller ID as being XIAFUSER (which is different from the ID I have created on the receiving SAP system) and is in function module IDOC_INBOUND_ASYNCHRONOUS. On XI, I have the RFC (SM59) and Port (IDX1) setup for the receiving SAP system. The receiving system has an ID setup (used in the RFC on XI), has a partner profile, port, logical system, and a RFC to XI setup.
Any ideas on where to track this down? I tried giving XIAFUSER sap_all, and it still fails and this ID does not exist on the receiving system.

HI,
Just to inform you that, if any SM58 error, mainly because of IDX1 entry and RFC destination .
So that;s the reason , i just suggested to check this SAP note.
Now you have given SAP_ALL access to test right ? Even you can check with this SAP note-837595
Also check that SM59 (RFC destination) in XI system uses any User ID ? DO not select CURRENT USER option here.. and check it
Regards,
Moorthy

Goods receipt - IDOC (WMMBXY/WMMBID02) error

I am creating an inbound goods receipt with IDOC WMMBID02 and get the error 'Document date / / is incorrect in item 0000000001'. Error code: F5833.
Error Diagnosis: 'Service financial accounting: document date " / /" is technically incorrect in item "0000000001" of the accounting document.'
Anyone know why I get this error. Appears to be FI related.

Hi,
The error occurs in the following function module:
CALL FUNCTION 'DATE_CHECK_PLAUSIBILITY'
       EXPORTING
            DATE                      = I_BLDAT
       EXCEPTIONS
            PLAUSIBILITY_CHECK_FAILED = 01.
CHECK NOT SY-SUBRC IS INITIAL.
MESSAGE E833 WITH I_BLDAT I_POSNR.
Please check the documentation for the function module for details.
regards
Aveek

IDOC FIDCC1/FIDCCP02 - Error RW029

Similar Messages

Maybe you are looking for