Inbound IDOC receiver port not getting filled in
Hi All,
I checked the WE20 configuration and it is fine. Just wanted to check if there is any other sap configuration which might be missing.
The IDOC is coming from a web server and they confirmed that they are filling the receiver port information while sending, but in the IDOC that we receive in SAP the receiver port is coming as blank.
Any pointers will be appreciated.
Thanks,
Anil
Hello Anil,
When they say they are filling receiver port that means they filling EDIDC-RCVPRT, please note with out receiver port you will not be able to receive the Idoc.
It means this value might be cleared somewhere in SAP. may be user exit or BADI or enhancement. what you can do is try to create inbound idocs by populating receiver port using WE19 and check whether the created idoc contains this value or not.By doing the you can get an idea where this value is disappered.
Similar Messages
-
Inbound Idoc - Date fields not getting saved
Hello,
I have created inbound idoc scenario in SAP. I receive Idoc from non SAP system to SAP system.
then data from IDoc is saved into different tables, for that I have written one function module (attached to process code)
One of the segments in IDoc type has date as a field. It is of type sy-datum.
When I receive Idoc in SAP only date fields are not getting saved in tables.
Is anything specific need to be done for date fields? please advice.check which format you are getting into sap and make sure you are coverting in into required format.
-
XI Idoc Receiver Port Not Found
Hi there
I have a Idoc Scenario where the Idoc is a receiver adapter going into some Sap System. I have setup the scenario and it gets processed correctly but the Idoc has got a status 56. Everything seems fine but in WE02, if I view the idoc under Technical Info, the Port there is different from what I have specified in the message mapping. Where does that port get specify if not in XI?
Thanx,
JanHi Jan,
have a look at my blog
/people/michal.krawczyk2/blog/2005/09/01/xi-idoc-adapter--edidc40--demystified
to understand which values from the control record you can control
and how
Regards,
Michal Krawczyk -
Structure is not getting filled in the subroutine
Hi Gurus,
I'm working on a Z-report ZMB52 for fetching Reserved Stock and showing it in a column.
The following code in a subroutine I've written for the same.
DATA: GS_RESB LIKE LINE OF GT_RESB.
CLEAR: BESTAND.
IF BESTAND[] IS NOT INITIAL.
SELECT MATNR
BDMNG
FROM RESB
INTO TABLE GT_RESB
FOR ALL ENTRIES IN BESTAND[]
WHERE MATNR EQ BESTAND-MATNR.
IF SY-SUBRC EQ 0.
SORT GT_RESB BY MATNR.
LOOP AT BESTAND.
READ TABLE GT_RESB INTO GS_RESB WITH KEY MATNR = BESTAND-MATNR. "BINARY SEARCH.
IF SY-SUBRC EQ 0.
MODIFY BESTAND TRANSPORTING BDMNG WHERE MATNR = BESTAND-MATNR.
ENDIF.
CLEAR: BESTAND, GS_RESB.
ENDLOOP.
ENDIF.
ENDIF.
When I debug, I can see that the structure GS_RESB is not getting filled through the READ TABLE statement. However, GT_RESB shows the data.
Could you please tell me where am I going wrong and a way to correct it?
Thanks in Advance!
Best Regards,
Ashutosh.Hi Joshi
You can use
LOOP AT GT_RESB INTO GS_RESB WHERE MATNR = BESTAND-MATNR. "BINARY SEARCH.
MODIFY BESTAND TRANSPORTING BDMNG WHERE MATNR = BESTAND-MATNR.
CLEAR: BESTAND, GS_RESB.
ENDLOOP.
And please check in debug BESTAND-MATNR .
Best regards. -
IT_FIELDCATALOG IS NOT GETTING FILLED
HI friends
I have returned a program for workflow tracking. Am getting the output has led light alone no data's are displayed. I found that my IT_FIELDCATALOG = GT_FCAT is not getting filled. How to fill that. Am pasting my programming here. Kinldy help me out.
TYPE-POOLS: ABAP.
TABLES : PTREQ_ATTABSDATA,PTREQ_HEADER,PTREQ_ITEMS.
TYPES: BEGIN OF TY_S_OUTTAB,
EXCEPTION TYPE LVC_EXLED,
PERNR TYPE P0001-PERNR,
BEGDA TYPE PTREQ_ATTABSDATA-BEGDA,
ENDDA TYPE PTREQ_ATTABSDATA-ENDDA,
SUBTY TYPE SUBTY,
STATUS TYPE PTREQ_HEADER-STATUS,
END OF TY_S_OUTTAB.
TYPES: TY_T_OUTTAB TYPE STANDARD TABLE OF TY_S_OUTTAB
WITH DEFAULT KEY.
DATA : REQUEST_ID TYPE PTREQ_HEADER-REQUEST_ID.
DATA:
GD_REPID TYPE SYREPID,
GD_OKCODE TYPE UI_FUNC,
GT_FCAT TYPE LVC_T_FCAT,
GS_LAYOUT TYPE LVC_S_LAYO,
GS_VARIANT TYPE DISVARIANT,
GO_DOCKING TYPE REF TO CL_GUI_DOCKING_CONTAINER,
GO_GRID TYPE REF TO CL_GUI_ALV_GRID.
DATA: FIELDCATALOG TYPE SLIS_T_FIELDCAT_ALV WITH HEADER LINE.
DATA: GT_OUTTAB TYPE TY_T_OUTTAB.
PARAMETERS:
PERNR TYPE PA0001-PERNR,
REQ_ID TYPE PTREQ_HEADER-REQUEST_ID,
LEA_TY TYPE PA0001-SUBTY,
BEGDA TYPE PA0001-BEGDA,
ENDDA TYPE PA0001-ENDDA.
REQ_ID = '52A08D487A9B5807E10000000A170133'.
START-OF-SELECTION.
BREAK-POINT.
* SELECT * FROM PTREQ_ATTABSDATA INTO CORRESPONDING FIELDS OF TABLE gt_outtab
* WHERE PERNR = PERNR AND SUBTY = LEA_TY.
SELECT C~PERNR C~BEGDA C~ENDDA C~SUBTY A~STATUS INTO CORRESPONDING FIELDS OF TABLE GT_OUTTAB
FROM ( ( PTREQ_HEADER AS A INNER JOIN
PTREQ_ITEMS AS B ON A~ITEM_LIST_ID = B~ITEM_LIST_ID ) INNER JOIN
PTREQ_ATTABSDATA AS C ON B~ITEM_INS = C~ITEM_ID )
WHERE REQUEST_ID = REQ_ID AND REQUEST_TYPE = 'ABSREQ'
AND VERSION_NO = ( SELECT MAX( VERSION_NO ) FROM PTREQ_HEADER
WHERE REQUEST_ID = REQ_ID ) AND
ITEM_LIST_NO = ( SELECT MAX( ITEM_LIST_NO )
FROM PTREQ_ITEMS WHERE ITEM_LIST_ID = A~ITEM_LIST_ID ) .
PERFORM INIT_CONTROLS.
PERFORM CHECK_CONDITION.
* Display data
CALL METHOD GO_GRID->SET_TABLE_FOR_FIRST_DISPLAY
EXPORTING
IS_LAYOUT = GS_LAYOUT
IS_VARIANT = GS_VARIANT
I_SAVE = 'A'
CHANGING
IT_OUTTAB = GT_OUTTAB
IT_FIELDCATALOG = GT_FCAT
EXCEPTIONS
OTHERS = 4.
IF SY-SUBRC = 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
* MESSAGE ID mid TYPE mtype NUMBER num.
ENDIF.
CALL SCREEN '0100'.
END-OF-SELECTION.
*& Module STATUS_0100 OUTPUT
* text
MODULE STATUS_0100 OUTPUT.
SET PF-STATUS 'STATUS_0100'.
* SET TITLEBAR 'xxx'.
** CALL METHOD go_grid1->refresh_table_display
*** EXPORTING
*** IS_STABLE =
*** I_SOFT_REFRESH =
** EXCEPTIONS
** FINISHED = 1
** others = 2
** IF sy-subrc 0.
*** MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*** WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
** ENDIF.
*OK-CODE->GD_OKCODE.
ENDMODULE. " STATUS_0100 OUTPUT
*& Module USER_COMMAND_0100 INPUT
* text
MODULE USER_COMMAND_0100 INPUT.
CASE GD_OKCODE.
WHEN 'BACK' OR
'END' OR
'CANC'.
SET SCREEN 0.
LEAVE SCREEN.
WHEN OTHERS.
CALL METHOD GO_GRID->REFRESH_TABLE_DISPLAY
EXCEPTIONS
FINISHED = 1
OTHERS = 2.
IF SY-SUBRC = 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDCASE.
CLEAR: GD_OKCODE.
ENDMODULE. " USER_COMMAND_0100 INPUT
*& Form INIT_CONTROLS
* text
* --> p1 text
* <-- p2 text
FORM INIT_CONTROLS .
* Create ALV grid
CREATE OBJECT GO_GRID
EXPORTING
I_PARENT = GO_DOCKING
EXCEPTIONS
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.
PERFORM BUILD_FIELDCATALOG.
PERFORM SET_LAYOUT_AND_VARIANT.
ENDFORM. " INIT_CONTROLS
*& Form BUILD_FIELDCATALOG
* text
* --> p1 text
* <-- p2 text
FORM BUILD_FIELDCATALOG.
*fieldcatalog-fieldname = 'EXPECTION'.
* fieldcatalog-seltext_m = 'LIGHT'.
* fieldcatalog-col_pos = 1.
* fieldcatalog-outputlen = 3.
** fieldcatalog-emphasize = 'X'.
* APPEND fieldcatalog TO fieldcatalog.
* CLEAR fieldcatalog.
FIELDCATALOG-FIELDNAME = 'PERNR'.
FIELDCATALOG-SELTEXT_M = 'EMPLOYEE NO'.
FIELDCATALOG-COL_POS = 1.
FIELDCATALOG-OUTPUTLEN = 8.
FIELDCATALOG-EMPHASIZE = 'X'.
APPEND FIELDCATALOG TO FIELDCATALOG.
CLEAR FIELDCATALOG.
FIELDCATALOG-FIELDNAME = 'REQ_ID'.
FIELDCATALOG-SELTEXT_M = 'REQUEST_ID'.
FIELDCATALOG-COL_POS = 2.
APPEND FIELDCATALOG TO FIELDCATALOG.
CLEAR FIELDCATALOG.
FIELDCATALOG-FIELDNAME = 'LEA_TY'.
FIELDCATALOG-SELTEXT_M = 'LEAVE_TYPE'.
FIELDCATALOG-COL_POS = 3.
APPEND FIELDCATALOG TO FIELDCATALOG.
CLEAR FIELDCATALOG.
FIELDCATALOG-FIELDNAME = 'BEGDA'.
FIELDCATALOG-SELTEXT_M = 'BEGIN_DATE'.
FIELDCATALOG-COL_POS = 4.
APPEND FIELDCATALOG TO FIELDCATALOG.
CLEAR FIELDCATALOG.
FIELDCATALOG-FIELDNAME = 'ENDDA'.
FIELDCATALOG-SELTEXT_M = 'END_DATE'.
FIELDCATALOG-COL_POS = 5.
APPEND FIELDCATALOG TO FIELDCATALOG.
CLEAR FIELDCATALOG.
FIELDCATALOG-FIELDNAME = 'STATUS'.
FIELDCATALOG-SELTEXT_M = 'STATUS'.
FIELDCATALOG-COL_POS = 6.
APPEND FIELDCATALOG TO FIELDCATALOG.
CLEAR FIELDCATALOG.
* define local data
DATA:
LS_FCAT TYPE LVC_S_FCAT.
CALL FUNCTION 'LVC_FIELDCATALOG_MERGE'
* EXPORTING
* I_BUFFER_ACTIVE =
* I_STRUCTURE_NAME = 'TY_S_OUTTAB'
* I_CLIENT_NEVER_DISPLAY = 'X'
* I_BYPASSING_BUFFER =
* I_INTERNAL_TABNAME =
CHANGING
CT_FIELDCAT = GT_FCAT
EXCEPTIONS
INCONSISTENT_INTERFACE = 1
PROGRAM_ERROR = 2
OTHERS = 3.
IF SY-SUBRC = 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " BUILD_FIELDCATALOG_KNB1
*& Form SET_LAYOUT_AND_VARIANT
* text
* --> p1 text
* <-- p2 text
FORM SET_LAYOUT_AND_VARIANT .
CLEAR: GS_LAYOUT,
GS_VARIANT.
* GS_LAYOUT-CWIDTH_OPT = ABAP_TRUE.
GS_LAYOUT-ZEBRA = ABAP_TRUE.
GS_LAYOUT-EXCP_FNAME = 'EXCEPTION'. " define column for LED
GS_LAYOUT-EXCP_LED = ABAP_TRUE.
GS_VARIANT-REPORT = SYST-REPID.
GS_VARIANT-HANDLE = 'GRID'.
ENDFORM. " SET_LAYOUT_AND_VARIANT
*& Form CHECK_CONDITION
* text
* --> p1 text
* <-- p2 text
FORM CHECK_CONDITION .
* define local data
DATA: LS_OUTTAB TYPE TY_S_OUTTAB.
LOOP AT GT_OUTTAB INTO LS_OUTTAB.
IF ( LS_OUTTAB-STATUS = 'APPROVED' ).
LS_OUTTAB-EXCEPTION = '3'. " GREEN LED/traffic light
ELSE.
LS_OUTTAB-EXCEPTION = '1'. " RED LED / traffic light
ENDIF.
MODIFY GT_OUTTAB FROM LS_OUTTAB INDEX SYST-TABIX.
ENDLOOP.
ENDFORM. " CHECK_CONDITION
Here in the function module 'LVC_FIELDCATALOG_MERGE'
GT_FACT is not getting filled. How to do that.
Regards
vijaysome thing you are missing, but any you can also do this..
change the definiton of the fieldcatalog.
DATA: FIELDCATALOG TYPE lvc_t_fcat WITH HEADER LINE.
population change
FIELDCATALOG-FIELDNAME = 'PERNR'.
FIELDCATALOG-COLTEXT = 'EMPLOYEE NO'.
FIELDCATALOG-COL_POS = 1.
FIELDCATALOG-OUTPUTLEN = 8.
FIELDCATALOG-EMPHASIZE = 'X'.
APPEND FIELDCATALOG TO FIELDCATALOG.
CLEAR FIELDCATALOG.
FIELDCATALOG-FIELDNAME = 'REQ_ID'.
FIELDCATALOG-COLTEXT = 'REQUEST_ID'.
FIELDCATALOG-COL_POS = 2.
APPEND FIELDCATALOG TO FIELDCATALOG.
CLEAR FIELDCATALOG.
FIELDCATALOG-FIELDNAME = 'LEA_TY'.
FIELDCATALOG-COLTEXT = 'LEAVE_TYPE'.
FIELDCATALOG-COL_POS = 3.
APPEND FIELDCATALOG TO FIELDCATALOG.
CLEAR FIELDCATALOG.
FIELDCATALOG-FIELDNAME = 'BEGDA'.
FIELDCATALOG-COLTEXT = 'BEGIN_DATE'.
FIELDCATALOG-COL_POS = 4.
APPEND FIELDCATALOG TO FIELDCATALOG.
CLEAR FIELDCATALOG.
FIELDCATALOG-FIELDNAME = 'ENDDA'.
FIELDCATALOG-COLTEXT = 'END_DATE'.
FIELDCATALOG-COL_POS = 5.
APPEND FIELDCATALOG TO FIELDCATALOG.
CLEAR FIELDCATALOG.
FIELDCATALOG-FIELDNAME = 'STATUS'.
FIELDCATALOG-COLTEXT = 'STATUS'.
FIELDCATALOG-COL_POS = 6.
APPEND FIELDCATALOG TO FIELDCATALOG.
CLEAR FIELDCATALOG.
method call display change..
* Display data
CALL METHOD GO_GRID->SET_TABLE_FOR_FIRST_DISPLAY
EXPORTING
IS_LAYOUT = GS_LAYOUT
IS_VARIANT = GS_VARIANT
I_SAVE = 'A'
CHANGING
IT_OUTTAB = GT_OUTTAB
IT_FIELDCATALOG = FIELDCATALOG[]
EXCEPTIONS
OTHERS = 4.
IF SY-SUBRC EQ 0.
ENDIF.
apply all the changes and see... -
Creating Delivery based on the Inbound IDOC received.
Hi all,
I have a requirement where in, Outbound Delivery for Sales order is to be created based on the inbound IDOC received from a third party. The standard idoc type DELIVERY03, requires the Delivery Number for updating the order but it cannot create a delivery number.
Can any one suggest which IDOC type can be used for this or if there is any alternative solution?Hi,
You can use FM IDOC_INBOUND_WRITE_TO_DB to create an inbound IDoc.
CALL FUNCTION 'IDOC_INBOUND_WRITE_TO_DB'
EXPORTING
PI_STATUS_MESSAGE = I_EDIDS
IMPORTING
PE_IDOC_NUMBER = DOCNUM
PE_STATE_OF_PROCESSING = STPROC
PE_INBOUND_PROCESS_DATA = I_TEDE2
TABLES
T_DATA_RECORDS = I_EDIDD
CHANGING
PC_CONTROL_RECORD = I_EDIDC
EXCEPTIONS
IDOC_NOT_SAVED = 1
OTHERS = 2.
Check the following link:
http://www.sapbrain.com/TUTORIALS/TECHNICAL/IDOC_tutorial.html
<b>Reward points</b>
Regards -
Requested Delivery Date not getting filled in ET_SALES
Hi Experts,
I am trying to read the Requested Delivery Date from FM CRM_ORDER_READ --> ET_SALES before the order is SAVED.
But the ET_SALES --> REQ_DLV_DAT is not getting filled until the Order is saved.
However, ET_SCHEDLIN --> FROM_TIME is getting filled even before the order is saved.
Is this standard functionality or am I missing on something?Hi,
In case you have missed on regular delta then you don't have any other choice than to selectively delete reciord from Infoprovider in case there is only cube..
If DSO in between with overwrite just load the records in DSO and check what is change log for this record.
If you can selectively load you can selectively delete for recent period..load again for that period in set up table then to SAP BW through full repair option.
Thanks and regards -
Setup tables not getting filled.
Hi all,
I am using MM module which includes purchasing data, i have identified 2lis_02_itm, 2lis_02_cgr, 2lis_02_scn, 2lis_02_sgr data sources for extracting purchasing data.
While extracting data from R/3 for data sources 2lis_02_cgr, 2lis_02_scn the setup tables were not getting filled. i followed all the standard procedures. i tried checking in RSA3 also but the no. of records was 0.
then i checked in NPRT t-code using the run name it was showing no. of docs. but when i extract data from R/3 to BW Processing: No data . 0 records.
Can anyone please help me in this issue?
Why are the setup tables not filled?
i have checked many threads regarding this issue ...but have no solution....
Thank you in advance.
Edited by: Jasmine G on Apr 21, 2008 10:32 AMApplication Number for Purchase is 02
So OLI3BW will not fill the Purchase related setup tables.
Best way is
T-code = SBIW
-> Settings for Application-Specific DataSources (PI)
-> Logistics
-> Managing Extract Structures
-> Initialization
-> Filling up the setup tables
-> Application-Specific Setup of Statistical Data
-> Then select the app for which you want to fill setup table
Rgds,
Vikram. -
"Receiver port not valid in control record"...idoc error
Hi,
The new materials are sent to SAP via a text file which is placed in the application server which EDI uses to populate the Idoc segments and creates the material master.
Recently we upgraded from SAP 4.6 C to ERP 5.0.
After upgrading we are getting a message as Port(HPLED) invalid in control record.
I get an error message as "receiver port HPLED not valid in control record"...
It is not able to find the receiver port & hence cannot create the MM.
We checked all the config and compared with Test and production and we could not find any noticable change.
Did anyone come across any infor on this?
Your valubale reply is really very important for me.
Pls reply.
Regards,
PriHey Ramesh,
I've already done the WE57 setting.
You see the WE57 setting is always done on the reciever side and not on the sender side (There is no harm but it is not what SAP recomends) The Linking on the sender side is done in the Partner Profile, where we give the extension name.
For the reciever this Partner profile setting of extension is not there therefore we need to go to WE57 and do it.
I've done all the config and have tried all the things in both the systems but somehow nothing is working.
That is why I asked that in my Inbound FM which is IDOC_INPUT_HRMD do I need to popluate one of it Parameters or fields where I mention the Extension name and all.
Yesterday however I found an SAP NOTE (105148) which tells me that my naming convention of the Extension is wrong. I have made ZHRMD_A07 extending standard IDOC tupe HRMD_A07, actually it should be ZRMD_A07. Again this is speculative I need to try this out. But I do know that SAP has various checks which checks all the naming convention and all. I'll try this out and hopefully it might work.
In the meantime any other suggestions are most invited. I am using Message type HRMD_A and using IDOC type HRM_A07
Regards
Abhishek Sahi -
Idoc - Partner Function not getting captured.
Dear all,
I am using IDOC (type - /NFM/ORDERS05) to send a Purchase Order. The Idoc is getting created but the only a few partner function is getting captured from the Partners tab in the ME22n transaction. The remaining partner functions that are not captured are SP (Forwarding Agent) and ER (Employee responsible).
Any bright ideas how to solve this problem.
Points will be awarded.Hi Vivek,
Thanks for your reply.
1. Where do i have set the receiver port and the message type for each "partner fuction". We do this generally for a Partner Type. (Please clarify)
2. If I remove the syntax check box then my PO is not getting created in ME21n transaction.
3. I have checked the Partner types there is not problem with that.
Regards,
Gajanan. -
IDOC - Function Exit not getting triggered
I am doing an inbound IDOC for the message type WMMBXY and using basic type WMMBID02.
This is for goods movement based on PO.
I am doing an enhancement in the includeof the function module exit EXIT_SAPLLMDE_002.
This exit is supposed to get triggered for the message type WMMBXY.
when i tested the idoc in we19 it is sucessfully getting posted. I want to check my code in EXIT_SAPLLMDE_002. I have set breakpoint and tested using we19. But this is not getting triggered. But the idoc is getting sucessfully posted but with a status message 56 An inbound partner profile could not be found( I am not sure if this has something to do with above problem).Did you attach your exit to a CMOD project and activated the same(CMOD transaction)?
The error you see regarding the partner profiles is probably due to the non existance of a partner profile for your idoc type in we20 transaction.
Maintain the inbound partner profile in we20 transacttion. -
IDOC status 64 not getting processed.
Hi Gurus,
I have a problem where IDOC's with status 64 are not getting processed via background job. the IDOCs weere getting processed with the background job till today evening, but suddenly no changes were made and the processing of IDOC's with status 64 has stopped and they keep filling up, when i checked the log of the Background job it says finished, and the log has the following information,
17.09.2009 19:05:23 Job started 00 516 S
17.09.2009 19:05:23 Step 001 started (program RBDAPP01, variant POS_IDOCS, user ID SAPAUDIT) 00 550 S
17.09.2009 19:05:25 No data could be selected. B1 083 I
17.09.2009 19:05:25 Job finished 00 517 S
Kindly advise on this.
Regards,
Riaz.When i process the IDOC's using BD87, they gets processed wiwth out aany issues no dump is displayed, idoc gets a status 53 after processing via BD87.
There is another problem how ever there are other jobs scheduled to run in the background other than this background job which are getting cancelled and have two different error logs for different jobs they are as follows.
1) 18.09.2009 02:00:06 Job started 00 516 S
18.09.2009 02:00:06 Logon not possible (error in license check) 00 179 E
18.09.2009 02:00:06 Job cancelled after system exception ERROR_MESSAGE 00 564 A
2) 18.09.2009 00:55:27 Job started 00 516 S
18.09.2009 00:55:27 Step 001 started (program RSCOLL00, variant , user ID JGERARDO) 00 550 S
18.09.2009 00:55:29 Clean_Plan:Gestartet von RSDBPREV DB6PM 000 S
18.09.2009 00:55:29 Clean_Plan:beendet DB6PM 000 S
18.09.2009 01:00:52 ABAP/4 processor: DBIF_RSQL_SQL_ERROR 00 671 A
18.09.2009 01:00:52 Job cancelled 00 518 A
This is a production server and the Licence is valid till 31.12.9999, and has no issues with the license. -
Inbound idoc application document not posted
Hi,
idoc status is 51 i.e. application document not posted.. when im tyring to send the cm data to other system it is successfull and doing some modifications in that and the same is sent from the other non-sap system to sap system.
During the sending from non-sap to sap system, the inbound idoc is getting the error as 51. and also providing some field name as kna1-cassd is not an input field.
This field is not being provided with any value but still the idoc is getting error with this field.
"Even i tried in the sap system itself, taking some sample data tested in we19 and executing with inbound idoc f.m:IDOC_INPUT_DEBITOR.. still the idoc is getting error message as 51 (with the same field).
Please provide your valuable suggestions to solve this problem.
I had created one cm and tried but still the same message is comming.
Awaiting your help.
thanks
rohithThanks for all your suggestions..
The problem is that im using the standard function module:IDOC_INPUT_DEBITOR..
So, this function module cannot be modified which is not my requirement.
My requirement is that i will send an outbound idoc to some non-sap system and now the non-sap system will make some modifications and resent to sap system (here in sap it is an inbound processing).
So, during inbound processing the status is showing as 51 due to the field kna1-cassd..
So i cannot make any customization but the inbound processing should be done and it should be saved into the db...
Hope you have got a clear requirement.
Waiting for your response.
Thanks
rohith -
Inbound Idoc INVOIC01: Balance not zero
In ECC 6.0, we are using inbound idoc type INVOIC01 and function module
IDOC_INPUT_INVOIC_MRM to enter MM invoices & FI-postings for incoming purchase
invoices that processed in an external system.
The idoc raises error msg M8 534: "Balance does not equal zero".
While processing the idoc, tax amount is not getting posted.
I tried posting invoice through MIRO using the same data and it is getting posted but when i am using idoc , its giving error.
Has anybody run into a similar problem? Any hint would be extremely valuable in order to solve the problem!Can anyone please help me on this ?
-
RFC receiver adapter not getting timed out
Hello Everyone,
I have a scenario like this:
Web-Service --> PI -->RFC (using receiver RFC channel)-->Response back to PI from RFC --> response back to Web-Service
This RFC is taking more than 5 minutes to give response back to PI but still I am not getting timeout in PI.
xiadapter.inbound.timeout.default is set to default value 180000.
Is there any other place where I should check for setting timeout like 10 seconds for rfc receiver channel?
Thanks,
SatarupaDear Satarupa,
You need to set ICM timeouts at Integration Engine level.
So go to SXMB_ADM and clic on Specific configuration. Edit table and set parameter as follow:
Category = RUNTIME.
Parameters = HTTP_TIMEOUT.
Current Value = [segs] depens your needs.
If you hasn't this parameter in SXMB_ADM set this parameter yourself.
Related link.
http://itsiti.com/increase-sap-icm-http_timeout-runtime
Regards,
Jose
Maybe you are looking for
-
Is there an instruction sheet detailing how to install Photoshop Elements 13 (from a DVD disk), on a Windows 8.1 computer, and if so, where do I find it?
-
Funky changes in itunes when I went from ipod mini to video ipod
I had an ipod mini. Just got a video ipod. Ever since I got the video ipod and hooked it up to my computer for the first time, when I play music in itunes, it will only play the song that I click on, it won't play subsequent songs and if I click on t
-
Hi support guys ! Nearly, I just bought a Ipad2 3G 32G white. I have updated to Ios5 for my ipad2. It 's problem that wifi signal of Ipad is not full althought my ipad was put nearly access point. Distance from ipad to access point is 3 or 4m. Wifi s
-
Embed html form into lightbox?
Why won't my Formscentral form embed? I need it to be a pop-up, but it won't work within a composition lightbox. I had some success with a composition tooltip, but the close button won't work, it doesn't seem to be connected to the pop-up because it'
-
Change documents for the custom transaction
hi, how could we trap the changes in our custom transaction to CDHDR,CDPOS tables. we had created the object and generated update information. where exactly we should call our write_document function module (generated in the object class ) in our mo