Getting error in idoc FD 008

Hello ,
i am getting an error in idoc which is related with Tax code & Tax rate conversion in EDI . The Message number is FD 008 and message is "Assigning a new tax key for and VAT .000 not possible .
Can anyone please help me what could be possible cause of this error and how can i correct it.

hello,
see if your tax code has a correct value and it is not blank.
best regards,
swanand

Similar Messages

Regarding Getting Error in Idoc .... Outbound table not found

Hello everyone
I am working on ALE/Idoc, at the last i am getting error that idoc has created but cannot be send, I am using XML port (not file) so giving Physical Dictionary, please solve my problem where i have to change. please reply its urgent.
Thanks & Regards
Vimarsh B.

Dear,
The addon is a third party addon which was developed by CitiXSys. so the support is provided by the partner who developed the addon.
Go to the vendor Citixys for further support will give you a quick reply.
Regards
Apple

Getting error saying 'IDoc included in IDoc packet containing an error'.

hi experts
When I am processing idoc in LSMW, getting error saying 'IDoc included in IDoc packet containing an error'.I changed the packet size also but it was not resolved.
Can any one tell me how to resolve this.

Hi,
Check below link......
Getting error 51 saying 'IDoc included in IDoc packet containing an error'
even this link is not solving problem then check the aplication log to get exact error text.
Thanks,
Asit Purbey.

Getting Error in Idoc.

Hi all,
I m getting this error in idoc..
Entry in outbound table not found.
I doc number is generated..
also giving Program code ..check and tell me whr can i do change..
Following is program for idoc...
REPORT ZNA_IDOC .
*TABLES: CRMD_ORDERADM_I,CRMD_ORDERADM_H,CRMD_SCHEDLIN.
TABLES : ZNA_ID.
DATA : S_CTRL_REC LIKE EDIDC OCCURS 0 WITH HEADER LINE,"Idoc Control
*Record
KUNNR TYPE ZNA_ID-KUNNR, " SEGMENT ORDER DATA
VBELN TYPE ZNA_ID-VBELN.
*QUANTITY TYPE CRMT_SCHEDLIN_QUAN VALUE '1.000'.
DATA : ZORDER LIKE ZNA_ID OCCURS 0 WITH HEADER LINE.
DATA : T_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE. "Data Records
DATA : T_COMM_IDOC LIKE EDIDC OCCURS 0 WITH HEADER LINE. "Generated
"Communication IDOc
CONSTANTS :
C_ZRZSEG1 LIKE EDIDD-SEGNAM VALUE 'ZNA_I'.
PARAMETERS : ZID LIKE EDIDC-MESTYP DEFAULT 'ZID', "Message Type
C_RCVPRT LIKE EDIDC-RCVPRT DEFAULT 'LS', "Partner type of receiver
C_LOGSYS LIKE EDIDC-RCVPRN DEFAULT 'D11CLNT100',
C_RCVPOR LIKE EDIDC-RCVPOR DEFAULT 'A000000009',
C_SNDPOR LIKE EDIDC-SNDPOR DEFAULT 'A000000008',
C_SNDPRN LIKE EDIDC-SNDPRN DEFAULT 'D11CLNT210',
C_IDOCTP LIKE EDIDC-IDOCTP DEFAULT 'ZNA_IT',
C_SNDPRT LIKE EDIDC-SNDPRT DEFAULT 'LS'. "Destination System
***START-OF-SELECTION
START-OF-SELECTION.
PERFORM GENERATE_CONTROL_RECORD.
PERFORM SEND_IDOC.
*& Form generate_control_record
FORM GENERATE_CONTROL_RECORD .
S_CTRL_REC-RCVPOR = C_RCVPOR. "Receiver Port
S_CTRL_REC-MESTYP = ZID. "Message type
S_CTRL_REC-IDOCTP = C_IDOCTP. "Basic IDOC type
S_CTRL_REC-RCVPRT = C_RCVPRT. "Partner type of receiver
S_CTRL_REC-SNDPOR = C_SNDPOR. "SENDER PORT
S_CTRL_REC-RCVPRN = C_LOGSYS. "Partner number of receiver
S_CTRL_REC-SNDPRT = C_SNDPRT. "Sender Partner type
S_CTRL_REC-SNDPRN = C_SNDPRN. "Sender Partner Number
APPEND S_CTRL_REC.
ENDFORM. " generate_control_record
*& Form send_idoc
FORM SEND_IDOC.
*SELECT * FROM ZNA_ID INTO TABLE ZORDER.
ZORDER-KUNNR = '1'.
ZORDER-VBELN = '101'.
**ZORDER-QUANTITY = QUANTITY.
APPEND ZORDER.
T_EDIDD-SEGNAM = C_ZRZSEG1.
T_EDIDD-SDATA = ZORDER.
APPEND T_EDIDD.
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
EXPORTING
MASTER_IDOC_CONTROL = S_CTRL_REC
TABLES
COMMUNICATION_IDOC_CONTROL = T_COMM_IDOC
MASTER_IDOC_DATA = T_EDIDD
EXCEPTIONS
ERROR_IN_IDOC_CONTROL = 1
ERROR_WRITING_IDOC_STATUS = 2
ERROR_IN_IDOC_DATA = 3
SENDING_LOGICAL_SYSTEM_UNKNOWN = 4
OTHERS = 5.
IF SY-SUBRC = 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ELSE.
COMMIT WORK.
LOOP AT T_COMM_IDOC.
WRITE:/ 'IDoc Generated - ', T_COMM_IDOC-DOCNUM.
ENDLOOP.
ENDIF.
ENDFORM. " send_idoc
thx...

The program is probably correct, however, it seems that you haven't completed the 'customizing' just yet. The parameters entered in S_CTRL_REC contains entries which have not yet been maintained in the settings.
Have a look at the settings. I have no SAP system available right now, so I can't tell you what transaction is needed, but first have look at WE20 (use transaction menu WEDI).

Hey friends ! Getting error in IDOC creation ! need help

After i execute the outbound IDOC report ! I am getting an error in the Status message as "error 26".
I searched for thet in se16 and come to know that its aEDI syntax error.
Can anyone tell Where are the defects and will be the approach to solve the error.In what way I will rectify !
Need your Advice on that.Thanks !

we19 will allow to re-execute & debug.

Getting error 51 saying 'IDoc included in IDoc packet containing an error'

When I am processing idoc in LSMW, getting error saying 'IDoc included in IDoc packet containing an error'.
Can any one tell me how to resolve this.

Hi,
Change the packet size to 1 then process again.

Getting error code 37 while sending IDOC via WE19

Hello experts,
I am facing a very unlikely error which is preventing me from testing my scenario.
I dont have XI quality server and hence I am using my development server as both dev and quality. Hence I need to connect both dev and quality SAP R/3 system to my XI dev system. While I have done all the configurations in my XI and both SAP R/3 systems, its giving me error when i am trying to send IDOC from quality system.
In quality R/3 i have done the following:
1) Created RFC for my XI dev server
2) Created port for this RFC
3) Created partner profile adding all required IDOCS in the outbound parameters
4) Created distribution channel for all the idocs
In XI dev system i have done the following:
1) Created RFC for both dev and quality of R/3
2) Created port for both the RFCs
3) Maintained the IDOC metadata for both the ports
Now when I am pusing IDOC via dev of r/3 (we19) is working fine but when I am doing the same from quality of r/3 its giving me status code of idoc as 37 that says "An error was identified in the control record while adding an IDoc. The sender port SAPQTY_510 is invalid."
But I have created this sender port SAPQTY_510 in my XI dev system and have also maintained the idoc metadata. I dont know why this error is coming.
Can anyone please point out what mistake i have done or if i missed sometig as I am trying to connect 2 r/3 systems to one XI system.
Its really urgent hence your help will be highly apreciated.
Thanks,
Yash

hi yash,
where you created SAPQTY_510 ,it should be created in R/3 Quality RFC destinations.
In XI DEV create port like SAPxxx WHERE xxx is SID of quality system.
actually we are getting confused.
i guess you used same name SAPQTY_510 in quality R/3 and XI DEV .
In error it says sender port SAPQTY_510 is invalid mean port of Source not XI DEV(receiver).
just try to use some other name say SAPXXX_QUA and confirm the error.
when IDOC is sent to XI DEV ,port of XIDEV SAPQTY_510 has nothing to play any role .
just check whether rfc destination of sender port (QUALITY R/3)you used is of type 3.
so please check at which port error is coming.
Thanks & Regards,
Rama Krishna
Edited by: rama krishna talluri on Mar 5, 2008 10:02 AM

Getting Error in SM58 and IDX2 while using IDOC from

Dear All,
Getting error when trying to send FIDCCP02 Idoc from ECC to PI system.
"Basic Type 'FIDCCP02' is unknown"
Getting the same error while trying to import metadata using IDX2 from PI side.
All connections and distribution model are created.
Please help
Regards

hey,
I checked all config again but getting error while checking ocnsistency in BDM5 on ECC system(E1Q).
It is failing when the messge type FIDCC1 reaches PI QA (X1Q) system and the error states
Message type FIDCC1 is not defined
Please check last line of below message:
E1QCLNT001     Checks in own system E1QCLNT001
     Message type     @08\QCheck OK@     Message type FIDCC1 is defined
     Segment filtering     @08\QCheck OK@     No segment filtering
     Conversions     @08\QCheck OK@     No conversion
     Partner profile     @08\QCheck OK@     Partner profile has been created
                                @08\QCheck OK@     .....Port PI_QA
          @08\QCheck OK@     .....Port PI_QA
          @08\QCheck OK@     .....Packet size 0001
          @08\QCheck OK@     .....Basis type FIDCCP02
          @08\QCheck OK@     .....enhancement
     Port     @08\QCheck OK@     Port PI_QA : To PI Quality System
          @08\QCheck OK@     .....Port type: Transactional RFC
          @08\QCheck OK@     .....port version 3: IDoc record types from Version 4.0 onwards
          @08\QCheck OK@     .....Logical address (destination) X1QCLNT001
     Logical address (destination)     @08\QCheck OK@     Logical address (destination) X1QCLNT001 is defined
X1QCLNT001     Checks in partner system X1QCLNT001
     Check of own logical system     @08\QCheck OK@     Own logical system is X1QCLNT001
          @08\QCheck OK@     Logical system is the same as the target address
                   Message Type     *@0A\QCheck resulted in error@*     Message type FIDCC1 is not defined
When I am clicking on error it is taking to WE81 on PI side.
So do I need to add this message type in PI system as it is present in ECC side?
Thanks
Edited by: Chanakya Sharma on Dec 10, 2010 12:10 PM

Getting error RVTBM-008 and RVTBM-120 during receiving RMA line

Hello,
Initially we tried to receive the RMA line but here we forgot to setup the lot number hence i am getting error when i was run the receiving transaction processor.
Then i put the correct LOT number and again delete all the lines from 'Receiving Transaction Summary' and tried to receive the RMA line in Inventory but i am getting below error when the Receiving Transaction Processor run.
Concurrent program RVCTP returned error
Cause: RVCTP encountered an internal error. Parameters: RVCTP,IMMEDIATE,584656,
Action: Note both this error number and the actions you are trying to perform. Contact your system ad
RVTBM-008: Subroutine rvtbm_immediate_mngr() returned error
Cause: Subroutine rvtbm_immediate_mngr() returned an internal error.
Action: Note this error number and the actions you are trying to perform. Contact your syste
RVTBM-120: Subroutine rvtptcontrol() returned error
Cause: Subroutine rvtptcontrol() returned an internal error.
Action: Note this error number and the actions you are trying to perform. Contact your system administrator
Concurrent Manager encountered an error while attempting to start your immediate concurrent program RVCTP. Routine &ROUTINE received a return code of failure.
Contact your support representative.
I am using Apps version-12.0.6
Please help me to rectify this issue.
Thanks,
Rajesh

Action: Note both this error number and the actions you are trying to perform. Contact your system ad
RVTBM-008: Subroutine rvtbm_immediate_mngr() returned error
Cause: Subroutine rvtbm_immediate_mngr() returned an internal error.
Action: Note this error number and the actions you are trying to perform. Contact your syste
RVTBM-120: Subroutine rvtptcontrol() returned errorSearch MOS for the above two errors and go through the docs.
RMA Deliver Transactions Stuck in RVCTP With RVTPT-020: Rvtoe_rmapushapi() [ID 278993.1]
UNABLE TO MAKE RECEIPTS AGAINST RMA User-Defined Exception in Package [ID 1082586.1]
RCVRCERC: Some RMAs fail with RVTBM-008: Subroutine rvtbm_immediate_mngr() returned error [ID 738890.1]
RVTII-030 rvtiicreate() When Receiving some RMA [ID 371464.1]
RVTBM-008: Subroutine rvtbm_immediate_mngr() returned error in Depot Repair Bulk Receiving [ID 1301960.1]
Thanks,
Hussein

Idoc ACC_GL_POSTING in batch input mode gets error

hi,
In ACC_GL_POSTING, msg type ACC_GL_POSTING01 with process code 'BAPI' it is working fine for me if i run normally.
whereas in transaction 'OBA7' for document type 'SA' if I set batch input only enabled i get error message 'Document type SA is only defined for batch input'. what is problem and how to solve it.
thanks in advance.

Team
I have been ckecking the problem and the problem is not FF68; it has more focuses with BSEG-ZFBDT and use of SGL indicators, and according the explanation below described I have decided to take other approach to resolve the problem.
"Please note that the due date field is as per standard design as per the SAP note 95079.
Field BSEG-ZFBDT is hardcoded in most FI screens to be mandatory and cannot be influenced by any field status changes. This situation only valid when posting with special G/L indicator (downpayment).
The reason behind this is that this special GL screen and the data entered here are very important to many other programs. This data affects liabilities and receivables where due date is necessary almost everytime."
I want to say many thanks to try to help me.
Ismael

Getting Error in ALE Service....

Hi All,
I am getting error when i am sending the IDOC...
The error is Entry in outbound table not found
Status 29
My selection Program is as following:
*& Report ZDS_CUST_IDOC
REPORT ZDS_CUST_IDOC MESSAGE-ID YM.
TABLES:ZDSCUSTHDR.
DATA: S_CONTROL_RECORD LIKE EDIDC, "IDOC CONTROL RECORD
 S_Z1DSEGMENT1 LIKE Z1DSEGMENT1. " CUSTOMER HEADER
DATA: T_CUSTHDR LIKE ZDSCUSTHDR OCCURS 0 WITH HEADER LINE,
 T_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE,
 T_COMM_IDOC LIKE EDIDC OCCURS 0 WITH HEADER LINE.
CONSTANTS: C_Z1SEG LIKE EDIDD-SEGNAM VALUE 'Z1DSEGMENT1'.
SELECT-OPTIONS : S_KUNNR for ZDSCUSTHDR-KUNNR.
START-OF-SELECTION.
PERFORM FETCH_CUSTHDR.
PERFORM CONTROL_REC.
PERFORM MASTER_IDOC_DISTRIBUTE.
END-OF-SELECTION.
*& Form FETCH_CUSTHDR
 text
--> p1 text
<-- p2 text
FORM FETCH_CUSTHDR .
SELECT *
FROM ZDSCUSTHDR
INTO TABLE T_CUSTHDR
WHERE KUNNR IN S_KUNNR.
LOOP AT T_CUSTHDR.
S_Z1DSEGMENT1-KUNNR = T_CUSTHDR-KUNNR.
S_Z1DSEGMENT1-NAME1 = T_CUSTHDR-NAME1.
S_Z1DSEGMENT1-ADD1 = T_CUSTHDR-ADD1.
S_Z1DSEGMENT1-REGIO = T_CUSTHDR-REGIO.
T_EDIDD-SEGNAM = C_Z1SEG.
T_EDIDD-SDATA = S_Z1DSEGMENT1.
APPEND T_EDIDD.
CLEAR T_EDIDD.
ENDLOOP.
ENDFORM. " FETCH_CUSTHDR
*& Form CONTROL_REC
 text
--> p1 text
<-- p2 text
FORM CONTROL_REC .
S_CONTROL_RECORD-MESTYP = 'ZDCUSHDR'. " MESSAGE TYPE
S_CONTROL_RECORD-IDOCTP = 'ZDCUSIDOC'. " BASIC IDOC TYPE
S_CONTROL_RECORD-RCVPRT = 'LS'. " PARTNER TYPE.
S_CONTROL_RECORD-RCVPRN = 'ZDCU810'. "PARTNER NO.
S_CONTROL_RECORD-RCVPOR = 'A000000068'. "PORT NO.
ENDFORM. " CONTROL_REC
*& Form MASTER_IDOC_DISTRIBUTE
 text
--> p1 text
<-- p2 text
FORM MASTER_IDOC_DISTRIBUTE .
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
EXPORTING
 MASTER_IDOC_CONTROL = S_CONTROL_RECORD
OBJ_TYPE = ''
CHNUM = ''
TABLES
 COMMUNICATION_IDOC_CONTROL = T_COMM_IDOC
 MASTER_IDOC_DATA = T_EDIDD
EXCEPTIONS
 ERROR_IN_IDOC_CONTROL = 1
 ERROR_WRITING_IDOC_STATUS = 2
 ERROR_IN_IDOC_DATA = 3
 SENDING_LOGICAL_SYSTEM_UNKNOWN = 4
 OTHERS = 5
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
LOOP AT T_COMM_IDOC.
WRITE:/ 'NO. OF IDOC GENERATED:',T_COMM_IDOC-DOCNUM.
ENDLOOP.
ENDFORM. " MASTER_IDOC_DISTRIBUTE
Please help me out asap.....
Regards,
Dhruv Shah

Hi Dhruv..
There are 2 issues:
1. Error 29 comes when u did not maintain the PARTNER PROFILE for this message type in Tcode WE20. Check it.
2. After calling the MASTER_IDOC_DISTRIBUTE you must execute COMMIT WORK.
START-OF-SELECTION.
PERFORM FETCH_CUSTHDR.
PERFORM CONTROL_REC.
PERFORM MASTER_IDOC_DISTRIBUTE.
commit work. "Updates the Communication Idocs in Database
Reward if Helpful.

Error sending Idoc's to SAP

Hi,
I'm getting error in file-XI-SAP scenario. File is read and transformed to Idoc ok, but then I get this kind of error message in SXMB_MONI:
<SAP:Stack>Error: Basic type 'HRMD_A01' is unknown</SAP:Stack>
What I'm I missing in the scenario?

Hi Tapio,
Take a look at this link:
http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
Error: No IDocs could be sent to the SAP BW using RFC.
Hope it helps you.
Cheers,
Chandra

Error in IDoc to file

hello all.......
i m doing a idoc to file scenario..and everything is going fine but the problem is::--
while the IDoc is generated and in integartion server it is getting posted under as some other message type which is not the one i used in the scenario..
So i am confused .
Pls help me in rectifing this.
waiting for ur valuable responses.
regards,
Ram

Hi ramdevbabu
Please explain the error ur getting ...
IS ur Idoc is posted to r/3 system ?
If ur getting red in SXMB_MONI
1.Check the receiver determination u created .
Is ur receiver determination is having proper
Sender service
 Sender Interface 
 sender interface namesapce
2.Check the configured receiver in RCV determination
and interface mapping
3. check the message XML message processing in SXMB_MONI and find out on which step ur getting error
Thanks
nagsen

Sender party of reciever determination is getting used in IDOC receiver

Hi All,
i am having a very strange problem in my XI scenarios.
i have 2 scenarios: S1 and S2.....S1 scenario is running on production.......S2 scenario is on development....both S1 and S2 are similar in the sense, they are sending IDOC to SAP R/3.......
s1 scenario is having in recever determination :
sender party A
sender service A1
receiver service R/3 by IDOC adapter - in this apply control rec values from payload is checked.......This S1 scenario is running fine on production.....
s2 scenario is having in recever determination :
sender party B
sender service B1
receiver R/3 bY IDOC adapter - in this when i check apply control rec values from payload, then in SXMB_MONI i get error :Unable to convert sender XI party http://sap.com/xi/XI/XIParty/B to an IDoc partner....So you see the sender party B is getting used in the IDOC comm channel......But when i uncheck control rec values from payload, then my msg is successfully processed in SXMB_MONI...
Now my question is : why S1 is runnig fine and S2 is not running fine on check apply control rec values from payload option......both are having party and service in sender.........So has it to do something with the definition of party......
Thanks,
Rajeev Gupta
Message was edited by:
RAJEEV GUPTA

Hi Bhavesh,
my scenario is file - idoc........basically it is XI msg->IDOC scenario....the source xi msg i am getting from another XI system.....but on dev, i cannot connect to that external XI system, so on dev i am having file sender adapter to send the source file to be mapped to IDOC and then to be send to R/3 dev..........
i saw the control rec values of both S1 of prd and S2 of dev........
S1 scenario is similar to S2 in the sense it also has XI msg from that external system.....but since prd is connected to that external XI system, so we have created a party and a business service in it.......it has in IDOC adpatere the option of appy control rec checked........
i saw that the control rec of both S1 and S2 msgs were similar......moreover the control rec values of S2 msg with and without the option of appy control rec checked were similar.........the only issue is when the apply control rec option is checked, then it gives error that "Unable to convert sender XI party http://sap.com/xi/XI/XIParty/B to an IDoc partner"......
But in S1 prd scenario, it is not giving this error on checking the option of appy control rec.......
Can you suggest why this is happening - why party B of S2 is considered differently from party A of S1......moreover these parties are simple parties created in ID.........
Thanks,
Rajeev Gupta

Error in IDOC generation

Hi Gurus,
I have got an Error in IDOC Processing from other interface.
The IDOC status is 51 and we are using it to create Promotion Deal in
SAP ERP through IDOC from other interface.
The Error i am getting in Status Record is that "Promotion is Duplicated
along with Promotion Deal Number"
I have also checked the Promotion Deal No in VB 33 but it is not existing.
Please could you suggest where is the possible error.
I have also checked the Control Record it is correct.
Awaiting for response.
Thanks,
Sam.
+

Hi,
Reprocess the IDOC by using the T.Code "BD87".
Even if the same error persists,try to change the data manually by using the T.Code "WE19".
Check with the ABAPer for debugging the code.
Regards,
Krishna.

Getting error in idoc FD 008

Similar Messages

Maybe you are looking for