IDOCs Problem

I am working on a custom program that will generate the list of all the idocs that have got errors in it and then we will fix the error and within the same program it will reprocess the idoc, now when I run this program and when I got the list of all the idocs with error and then I will manually correct the error in one of the idoc, once I am done with this then I will click on the tab which says reprocess idoc, as soon as I click on that tab one dialogue box pops up which says Reprocess idocs :
On the dialogue box it says
call transaction processing with the following three radio buttons:
1. In background
2. In foreground
3. In foreground after error
and by default it's taking In Background but I want to do tht as In foreground always, I mean the default radio button should set to Inforeground, when I tried to debug the program I figured it out that this particular screen is calling "SAPLSEUT" program but I am not being able to figure out how can i acheive this.
I think I need to make some changes in the following code, but don't know what exactly, it's a std. SAP program SAPLSEUT / LSEUTU04
if use_control = stree_use_control
and tv is initial.
call function 'RS_TREE_CONTROL_PREPARE'
EXPORTING
CONTROL_PATTERN = STREE_CTL_GENERIC
HIERARCHY_HEADER =
LIST_ITEM_HEADER =
MULTIPLE_SELECTION = STREE_FALSE
exceptions
not_available = 1
others = 2.
if sy-subrc 0.
use_control = stree_use_list.
endif.
endif.
case use_control.
when 'P'.
call screen 700.
when stree_use_list.
if screen_start_line = 0.
call screen 700.
else.
call screen 701
starting at screen_start_column screen_start_line
ending at screen_end_column screen_end_line.
endif.
when stree_use_control.
if screen_start_line = 0.
tv-popup = stree_false.
call screen 702.
else.
tv-popup = stree_true.
call screen 704
starting at screen_start_column screen_start_line
ending at screen_end_column screen_end_line.
endif.
call function 'CONTROL_DESTROY'
changing
h_control = tv-tree
exceptions
others = 1.
call function 'CONTROL_FLUSH'
exceptions
cntl_system_error = 1
cntl_error = 2
others = 3.
clear tv.
when stree_use_in_dynpro.
tv-subscreen = stree_true.
exit.
endcase.
pop
read table ld "wk070797
index 1. "wk070797
delete ld "wk070797
index 1. "wk070797
f15 = ld_f15.
clear:
ld_f15,
exit,
current_lsind,
cucol,
curow,
licol,
lirow,
tv.
refresh itree.
export tree
from itree
to memory
id logid.
if push_done = stree_true. "wk061109
call function 'RS_TREE_POP'.
endif. "wk061109
endfunction.
Edited by: Alvaro Tejada Galindo on Apr 30, 2008 3:08 PM

I was looking into the code again and I found that it;s hitting the custom program and a screen is being called with the follwoing code:
PROCESS BEFORE OUTPUT.
MODULE STATUS_0520.
MODULE INIT_DYNPRO_520.
PROCESS AFTER INPUT.
MODULE CANCEL_DYNPRO AT EXIT-COMMAND.
CHAIN.
FIELD MSED7PROCE-FCTNAME.
FIELD MSED7PROCE-SEL_FORGRD.
FIELD MSED7PROCE-SEL_BCKGRD.
FIELD MSED7PROCE-SEL_ERROR.
FIELD MSED7PROCE-SEL_DEBUG.
reaction on user command
MODULE USER_COMMAND_0520.
ENDCHAIN.
MODULE LEAVE_SCREEN.
I think if I take out :
FIELD MSED7PROCE-SEL_BCKGRD.
FIELD MSED7PROCE-SEL_ERROR.
FIELD MSED7PROCE-SEL_DEBUG.
from the above screen then I think it should take it foreground bydefault.
Please Advise
Thanks,
Rajeev Gupta

Similar Messages

Mapping with IDoc problem

Hi All
I am having a problem where if I get over about 30 records from my 3rd Party in a file. This data is mapped to the Materials Master IDoc(MATMAS05) and it gets a mapping error when trying to run thru the mapping.
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_MM_MATCAT_MATMAS_</SAP:P1>
<SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
<SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3>
If I take this data from the Payload in SXMB_MONI and test in the Graphical Mapping tool in Integration Design it crashes with the above error. If I take this file and break into 2 parts and then send thru the mapping tool both files has no error. Does anyopne have any idea why this error occurs(could this be a memroy error - but for like 30 records) and how I can fix this as we would like to do a mass upload - about 9000 records(materials).
Your help will be appreciated.
Thanks
Clinton

Hi
This is such a weird error.
I have now started taking this file that I receive from the 3rd party with 200 records and tested it with the mapping tool. The results are as follow: From record 1-31 goes successful, 32-147 goes successfully and 148-200 goes successfully. So if I take the file as one file it crash, but if I break the file into the above 3 files it goes thru fine. for the first part it can only take 31 records, the 115, and then the rest. This does not make any sense, can someone please give me some advise.
Thanks
Clinton

G/L Idoc problem

Hi All,
I am posting an invoice from a flat file. First of all i will execute the program RSEINB00 and input the file name. This program will create an idoc from the flat file.
Next, I will execute the program RBDAPP01 to process the idoc and post an invoice.
The problem i am facing is, When there are more no of lines (G/L accounts) in the file ( Say 5948 lines ) the created IDoc data records are as follows.
it has total 47872 segments. And it splits the idoc and each segment block is having 993 lines (G/L accounts).
Segments 000001 007951 - 993 lines
Segments 007952 015951 - 993 Lines
Segments 015952 023951 - 993 Lines
Segments 023952 031951 - 993 Lines
Segments 031952 039951 - 993 Lines
Segments 039952 047872 - 983 Lines.
It will create a BDC session and whn i process the session error comes "No batch input data for screen SAPMF05A 0700" after 949th line. When i see th OSS note it says "Invoices with more than 949 G/L account line items must be split".
My Question is Where can i do this setting inorder to restrict the G/L account lines to <949 in each segment block??
Any insights will be appreciated.

Hi Tushar,
You can add your own codes in user exit to restrict the G/L account lines to < 949 during creation each segment block.
Please search any user exits available in the function module which is used for inbound IDoc creation.
In this case, your BDC will not give an error message because you already handled the max lines for G/L account during creation an IDoc for batch input process.
Hope this will help.
Regards,
Ferry Lianto
Please reward points if helpful.

Inbound INVOIC01 IDOC problem

Hi,
I am working on inboind INVOIC01 idoc and i am facing some problem in that.
When IDOC comes in it is creating application document ( Status 53 ). When i go and check in transaction MIR4 the application document (Invoice) is created. But the problem is, the Invoice is not being posted.
When i see the invoice document, there is not tax code and so the invoice does not show any amount. I do not know why it is happening.
Can anyone let me know what are the all required segments / fields for inbound invoice interface. What are the all configuration options required for it.
Thanks,

Hi Srinivas,
Thanks for your reply.
I have already configured the tax code config and now invoices are created correctly.
But now i have one scenario which i am tying to figure out how to get it right.
Let say for example
Example - 1
- i have PO with 1 line iteam with Quantity = 1 and amount $100. ( we mostly have PO with quantity =1 and only thing matter is $ value )
- If the incoming invoice also have quantity = 1 and amount $100, it works fine.
- But the problem is, sometime vendor sends the partial invoice. that is, quantity = 1 but amount $ 50. There can be multiple invoice with same quantity as PO line item different amount at different time. In this case i am gettng "Account Determination" error ( message M8 147 ). Is there any way i can make this scenarion work. 80% of invoices comes like this. Please let me know
Example - 2
- i have PO with 1 line iteam with Quantity = 2 and amount $200.
- If the incoming invoice also have quantity = 1 and amount $100, it works fine. Also, if it has quant = 2 and amount $ 200 it works fine. In other workds the quantity / amount ratio in invoice matches that of PO, it works fine.
- But in few case we will get invoice with quantity = 1 ( PO as quant = 2) with amount 80 ( infact, any value other than 100. PO has $200, $100 / 1 each ) and in this case invoice is failing too.
Can you please let me know, is there any setting in Logistic Invoice Verification, to support these scenarios.
Thanks
Pratik

Add segment to inbound idoc problem

Hi ,
I want to insert a segment in the middle of the segements inside a inbound idoc processing module.The problem is
i am able to pass the segmnet name and data but i don't now what should be populated to the segment number (SEGNUM). Its value is coming as the same value of the previous segment when i checked in debugging mode.Can any body tell me how to populate the segnum field.
Regards,
Soumya.

Have you tried by just keeping it blank.I will work fine if the hierarchy is kept correctly.

Strange IDoc problem in new System

I am trying to post IDocs through a new production system that has just been set up. We have been running the scenario in the Test environment successfully for a few weeks.
I send a batch of IDocs to the system, for example a bunch of four IDocs. Sometimes all four will process fine, other times one or more of the IDocs gop into error with the message
There is no connection registered at the Messaging System for adapter type: File_http://sap.com/xi/XI/System
If I select the messages in the monitor, I can sometimes get the message through, and sometimes it reverts back to this error, perhaps requiring a few attempts to process successfully. Sometimes the message just will not process.
I am always resenfing four IDocs with the same data, so I really do not know what the problem could be.
Any answers appreciated!
BR,
Tony.

Hi,
NEVER delete the files manually. As a admins we have to follow proper Uninstall and reinstall procedures as above one gentle man said.
Here we will definately have some extra files also, like sapreorg, and backup file manually created if . Those also should be uninstalled properly.
Also, we should maintain one back up copy of our file systems in each servers.
just refer my system file structure, and proceed further.
http://img158.imageshack.us/img158/591/bdfll0.jpg
bye...

IDOC: Problem with data filter for IDOC extension field

Hallo!
I've created an idoc extension for the basic type DEBMAS06 that works fine. Now I want to use a data filter for one field ( company code ) of my segment. Every segment with a company code different from 100 should be filtered and not send to the other client. But what happend is that for all customers that have at least one company code different from 100, all segments including the one with cc 100 were deleted and a error "Segment ... does not exist for message type DEBMAS" appeared on the screen.
Does anyone have any ideas about this problem?

Not sure about changes to be made at the filtering options.
An alternative would be sending the data to XI as it is and perform the mapping to remove the unnecessary segments.
Disadvantage: Unnecessary processing of segment would be done at XI.
Advantage: The integration logic would be completely handled by XI.
Regards,
Prateek

Inbound - IDoc problem

Hi Friends,
Can anybody help me . I am facing a problem in IDOC inbound processing.
My scenario in SALES PER RECEIPT - POS like this: I have to read XML (From PC) file and i have to post it.
I am using Idoc - WPUBON01. After reading XML file i used Function module to distribute - MASTER_IDOC_DSTRIBUTE.
In we02 i checked Idoc is generating but status showing 29.
So run the report RSEOUT00. But i am getting message like 'No idoc is selected for processing'.
Plz help me what i have to do. I created port also.
Regards,
P. Kumar.

Hi,
sarath has told valid point..don't use master_idoc_distribute,instead use the bapi
bapi_idoc_input1..
plz check the sample code how to do with inbound idoc,as u have got the data ,u just need to call the bapi and post it..
check the code and proceed..
FUNCTION zdtsint052f_gpoms_to_sap_gm.
""Local interface:
*" IMPORTING
*" VALUE(INPUT_METHOD) LIKE BDWFAP_PAR-INPUTMETHD
*" VALUE(MASS_PROCESSING) LIKE BDWFAP_PAR-MASS_PROC
*" EXPORTING
*" VALUE(WORKFLOW_RESULT) LIKE BDWF_PARAM-RESULT
*" VALUE(APPLICATION_VARIABLE) LIKE BDWF_PARAM-APPL_VAR
*" VALUE(IN_UPDATE_TASK) LIKE BDWFAP_PAR-UPDATETASK
*" VALUE(CALL_TRANSACTION_DONE) LIKE BDWFAP_PAR-CALLTRANS
*" TABLES
*" IDOC_CONTRL STRUCTURE EDIDC
*" IDOC_DATA STRUCTURE EDIDD
*" IDOC_STATUS STRUCTURE BDIDOCSTAT
*" RETURN_VARIABLES STRUCTURE BDWFRETVAR
*" SERIALIZATION_INFO STRUCTURE BDI_SER
*" EXCEPTIONS
*" WRONG_FUNCTION_CALLED
Purpose :On recording the material consumption from *
 manufacturing tickets in GPOMS system, GPOMS *
 will report the data to the SAP system.Based *
 on this message, goods issue to the process order*
 will be posted in SAP. This interface will *
 used for storage location managed materials *
 in SAP. *
Program Logic :Loop at the data records of IDOC and to get the *
 Order number and SAP Movement type *
 If the Material document already exists for this *
 Order number and Movement type then give error *
 else call standard FM 'BAPI_IDOC_INPUT1' to *
 Material Documents in SAP. *
Declaration of Constants *
CONSTANTS :lc_item_create(25) TYPE c VALUE 'E1BP2017_GM_ITEM_CREATE',
 lc_mbgmcr(6) TYPE c VALUE 'MBGMCR'.
Declaration of Variables *
DATA : lv_index TYPE sytabix,
 lv_retcode type sy-subrc.
Declaration of Workareas *
DATA: lwa_e1bp2017_gm_item_create TYPE e1bp2017_gm_item_create,
 lwa_data TYPE edidd, " Work area for IDOC
 lwa_control TYPE edidc. " Work Area for control rec
Read the control data information of idoc.
loop at idoc_contrl INTO lwa_control Where mestyp = lc_mbgmcr.
Extract the data from the segments.
 LOOP AT idoc_data INTO lwa_data
 WHERE docnum = lwa_control-docnum and
 segnam = lc_item_create.
*->> Set the tabix of the internal table
 lv_index = sy-tabix.
Move the Material Document Item Segment data
 MOVE lwa_data-sdata TO lwa_e1bp2017_gm_item_create.
Modify the material document item data internal table
 PERFORM sub_modify_idocdata changing lwa_e1bp2017_gm_item_create.
*->> set the changed values to the IDOC SDATA
 MOVE lwa_e1bp2017_gm_item_create TO lwa_data-sdata.
*->> Modify the table
 MODIFY idoc_data FROM lwa_data index lv_index.
Clear the Work areas
 CLEAR : lwa_data,
 lwa_e1bp2017_gm_item_create.
 ENDLOOP. "LOOP AT t_idoc_data
Call the BAPI function module to create the
appropriate Material Document
 CALL FUNCTION 'BAPI_IDOC_INPUT1'
 EXPORTING
 input_method = input_method
 mass_processing = mass_processing
 IMPORTING
 workflow_result = workflow_result
 application_variable = application_variable
 in_update_task = in_update_task
 call_transaction_done = call_transaction_done
 TABLES
 idoc_contrl = idoc_contrl
 idoc_data = idoc_data
 idoc_status = idoc_status
 return_variables = return_variables
 serialization_info = serialization_info
 EXCEPTIONS
 wrong_function_called = 1
 OTHERS = 2.
 IF sy-subrc = 1.
 RAISE wrong_function_called.
 ENDIF.
endloop.
ENDFUNCTION.
***INCLUDE LZDTSINT052F_GPOMS_GMF01 .
*& Form sub_modify_idocdata
Modify the material document item data internal table
FORM sub_modify_idocdata
CHANGING pwa_e1bp2017_gm_item_create TYPE e1bp2017_gm_item_create.
contant declaration
CONSTANTS: lc_261(3) TYPE c VALUE '261'.
DATA : lv_aplzl LIKE resb-aplzl,
 lv_aufpl LIKE resb-aufpl,
 lv_subrc LIKE sy-subrc,
 lv_charg LIKE resb-charg,
 lv_uom LIKE pwa_e1bp2017_gm_item_create-entry_uom.
CLEAR: pwa_e1bp2017_gm_item_create-reserv_no,
 pwa_e1bp2017_gm_item_create-res_item.
*->> Get SAP storage bin & Storage type from the Z table
SELECT lgtyp lgpla
 INTO (pwa_e1bp2017_gm_item_create-stge_type,
 pwa_e1bp2017_gm_item_create-stge_bin)
 UP TO 1 ROWS
 FROM zdtsint050_sttyp
 WHERE zstorage_typ = pwa_e1bp2017_gm_item_create-stge_type
 AND zstorage_bin = pwa_e1bp2017_gm_item_create-stge_bin.
ENDSELECT.
IF sy-subrc NE 0.
 CLEAR: pwa_e1bp2017_gm_item_create-stge_type,
 pwa_e1bp2017_gm_item_create-stge_bin.
ENDIF.
PERFORM get_oper CHANGING pwa_e1bp2017_gm_item_create.
Get the Reservation number and Reservation item number
basing on the idoc data.
SELECT rspos werks lgort
 INTO (pwa_e1bp2017_gm_item_create-res_item,
 pwa_e1bp2017_gm_item_create-plant,
 pwa_e1bp2017_gm_item_create-stge_loc)
 FROM resb
 UP TO 1 ROWS
 WHERE rsnum = pwa_e1bp2017_gm_item_create-reserv_no
 AND matnr = pwa_e1bp2017_gm_item_create-material
 AND charg = pwa_e1bp2017_gm_item_create-batch
 AND aufnr = pwa_e1bp2017_gm_item_create-orderid
 AND vornr = pwa_e1bp2017_gm_item_create-activity
 AND bwart = lc_261.
ENDSELECT.
IF sy-subrc <> 0.
Start of insertion for R31K993797
 CLEAR lv_charg.
 SELECT rspos werks lgort
 INTO (pwa_e1bp2017_gm_item_create-res_item,
 pwa_e1bp2017_gm_item_create-plant,
 pwa_e1bp2017_gm_item_create-stge_loc)
 FROM resb
 UP TO 1 ROWS
 WHERE rsnum = pwa_e1bp2017_gm_item_create-reserv_no
 AND matnr = pwa_e1bp2017_gm_item_create-material
 AND charg = lv_charg
 AND aufnr = pwa_e1bp2017_gm_item_create-orderid
 AND vornr = pwa_e1bp2017_gm_item_create-activity
 AND ( splkz = 'X' or
 splkz = space )
 AND bwart = lc_261.
 ENDSELECT.
 IF sy-subrc <> 0.
End of insertion for R31K993797
 SELECT SINGLE werks lgort
 INTO (pwa_e1bp2017_gm_item_create-plant,
 pwa_e1bp2017_gm_item_create-stge_loc)
 FROM resb
 WHERE rsnum = pwa_e1bp2017_gm_item_create-reserv_no.
 CLEAR : pwa_e1bp2017_gm_item_create-reserv_no,
 pwa_e1bp2017_gm_item_create-res_item.
 ENDIF.
ENDIF.
get SAP UOM
SELECT SINGLE zsap_uom
 INTO lv_uom
 FROM zca_uom_conv
 WHERE zext_uom = pwa_e1bp2017_gm_item_create-entry_uom.
IF sy-subrc = 0.
 pwa_e1bp2017_gm_item_create-entry_uom = lv_uom.
ENDIF.
ENDFORM. " sub_modify_idocdata
*& Form get_oper
 Get the operation
 <--P_PWA_E1BP2017_GM_ITEM_CREATE_RE Segment
FORM get_oper CHANGING p_pwa_e1bp2017_gm_item_create TYPE
 e1bp2017_gm_item_create.
DATA : l_aufpl LIKE afko-aufpl,
 l_aplzl LIKE afvc-aplzl.
REFRESH : i_op.
UNPACK p_pwa_e1bp2017_gm_item_create-orderid TO
 p_pwa_e1bp2017_gm_item_create-orderid.
Get the reservation and routing number for the order
SELECT SINGLE
 rsnum
 aufpl
 FROM afko
 INTO (p_pwa_e1bp2017_gm_item_create-reserv_no,
 l_aufpl)
 WHERE aufnr = p_pwa_e1bp2017_gm_item_create-orderid.
IF sy-subrc = 0.
 CALL FUNCTION 'CONVERSION_EXIT_NUMCV_INPUT'
 EXPORTING
 input = p_pwa_e1bp2017_gm_item_create-activity
 IMPORTING
 output = p_pwa_e1bp2017_gm_item_create-activity.
ENDIF.
ENDFORM. " get_oper
i have modifeid the incoming data,in ur case its not needed ,only first few lines until the bapi u have to see..if u have any query let me know..
Regards,
Nagaraj

IDOC Problem From 46C To ECC6 For ORDERS05

Hello
I am trying to generate 46C version ORDERS05 basic type from ECC6 700 version.
Within WE20(Partner Profiles) I have set the Seg. release in IDOC type to 46C to generate the old 46C segment. When I run my test again the IDOC that was generated is still version 700.
Thanks for the help.
Joe

Gentlemen:
The problem around this statement:
ASSIGN (w_field) TO <fs_field>
is explained as follows:
1. In ABAP language, there are two ways for assigning a new value to a field-symbol.
- Sentence: ASSIGN (values) TO <my_field_symbol>.
In this case, the <my_field_symbol> receives from (w_field) the data type and value content of this variable. So, we keep that a FSymbol is assigned and, at the same time, receives an initial value.
- Sentence: <my_field_symbol> = '/' or <my_field_symbol> = my_var.
In this way, we only pass the content of the variable next to = sign. But before this, the field-symbol must had been assigned (using ASSIGN statement), in another case, the compiler raises an exception.
Following the example of Federico... I think he tried to assign a field like this (please, supose the program imports the structure of a database table with a standard function, into a internal table which is looped by the work area w_field ):
- If w_field contains 'BKPF-WERKS', so sentence ASSIGN will affect the field symbol, passing to this the data type and current content of table field BKPF-WERKS.
- If w_field contains 'BKPF-.INCLUDE': *the column .INCLUDE obviously is not associated with a data type... so our statement ASSIGN... TO... never pass any data type or value to our field-symbol. So that, this field is never initialized properly, and when inmmediately you try to execute something like this: <my_field_symbol> = '/', the game (program) is over.. XD
I hope this post was helpful for anyone...
Best Regards!!
RRG
ABAPer(u) - EVOLution

Message ORDERS05 IDOC problem

Hello everyone!!!
My name is Rocio, I'm a new developer on IDOCS and I have a problem with de message ORDERS05.
I'm forming an STANDARD INBOUNT IDOC for Transaction VA02
I want to put a field (Assignment - ZUONR ) that is on Header>Accounting. in VA02(Transaction).
I use the segment E1EDK02             QUALF       017 : Assignment Number
But when I generated my idoc, this field is ok, but when I go to see the order..this field doesn't appear its empty...
Can anyone help me because i don´t why is this happened?
And i need this file with an IDOC value. because we are going to use this value in the invoice.
Thanks for your help!!!
Title was edited by:
        Alvaro Tejada Galindo

Hi experts,
I take this post to ask a new (added) question:
We would like to know how to insert a value for ZUONR vía IDOC_INPUT_ORDERS
    We already know that we must implement user exit EXIT_SAPLVEDA_001 in order to get from one segment of the ORDERS IDOC the value we want to insert into ZUONR.
    But when we analyze the following logic of the function module we see that the way SAP is generating the order is vía call transaction of VA01, and it seems that there's no vbak-zuonr field in the bdcdata structure passed to the call transaction.
    We assume that we need to implement the user exit EXIT_SAPLVEDA_002 to append the vbak-zuonr field with the proper value to the bdcdata structure, but we would like to know if there is some previous note explaning the way to do it or if there's other easier way to reach the same result.
Thanks.

IDOC PROBLEM (STATUS - 51)

Hi Gurus,
I have two problems that we really need corrected as soon as possible.
1. Before the upgrade last friday night, outstanding IDOCs (51 error) were listed as IncomingInvoices. Now, they are being listed as zBUS2081.
Application document not posted 51
1.Goods Movement
2.zBUS2081
3.service entry
please change it from zBUS2081 back to IncomingInvoices.
2. We've been dealing with an annoying issue since the last major upgrade to SAP. That problem is refreshing. We'll be in transaction BD87, make a correction to an IDOC, back out of the IDOC, push the refresh button, and then we wait.....and wait.....and wait....until we go to the top left, and click the stop transaction option. Then we have to double click back on BD87, get our variant (again), resort the errors, then we're able to click on the edited IDOC option to process the corrected IDOC. Before the last major upgrade, we could make our changes, click the refresh button and BAM the screen would be updated immediately. This is the way it should be working. Would you please look into whatever is causing it to stall? It takes up quite a bit of time to stop the transaction, go back in, refetch the variant, etc. The extra work is unnecessary.
Provide the solution asap.
Regards,
Chiranjeevi.

Please stick to the Rules.
1. Post in the right forum - for IDOCs that will data transfer - now moved for you.
2. Do not say "ASAP" or otherwise express that you're in a hurry. You maybe - we're not. Any answers are made out of goodwill. It is considered by many very rude to try to hurry people up.
3. Don't post the same question in more than one forum. I've rejected the other one.
Did you copy and paste these issues out of your client/employers help desk?
matt

Idoc problem while loading

Hi Gurus,
I am getting error "Idocs missing: No end-confirmation arrived in the Warehouse from" while loading data from R3 to BW via process chain.
Can any one please suggest me how solve this problem.
Thanks in advance.
Regards
Tony

Hi,
It may be due to below reasons...
1. Check whether the Log Table is full in the BW side.
2. Check Whether the Connection to Source System is fine.
3. System might be busy , Many jobs running in system.
Go to SM58 in BW system , find TRFC queue with enteries for each LUW . U can come to know why IDOC is not processed by looking at the error there . Also check whether the job is finished successfully in Source System. U can process the LUW in Sm58 manually from Edit menu entry ....
Thanks
DSt

ALE IDOC Problem...

HI..
I am facing a problem on the inbound side.
If I check the IDoc in WE02, I am getting a status error as
"No status record was passed to ALE by the a"
Customised IDoc is used.
Please advise if you can Thnx

HI,
IAM GIVING A DOCUMENT WHICH HELPS YOU TO UNDERSTAND EASILY AND YOURSELF CAN WORKOUT WITH THIS REAL TIME SCENARIO WHICH TRANSFERS THE DATA BETWEEN TWO SYSTEMS.
Application Linking and Enabling (ALE)
In this document you will learn the step-by-step procedure to setup the ALE system and go through a transaction between two clients
For our purpose we have two clients
namely Client 100 and Client 200.
System name is SAPKDC (FOR BOTH 100 AND 200 CLIENTS).
Distribution of Material Master Data Between two Systems
1) SETUP LOGICAL SYSTEM: (Note: Do Not Create This Step)
To do this follow the following steps
Execute SALE Transaction Code
On The Screen Click on Sending and Receiving Systems.
Then Click on Logical Systems.
Then Click Defining Logical Systems.
Click New Entries Button
(E.g. (LG100 sending system)
(LG200 receiving system))
Enter two logical system names and their description.
Save
Comeback to SALE Transaction Code screen.
2) Now you have to allocate the created logical systems to respective clients.( Note: Do Not Create This Step)
LG100 assign to client 100
LG200 assign to client 200
To do this, do the following.
Click Assigning Client to Logical System.
Ignore the message that comes up on the screen.
Select client 100
Click details button on the toolbar icon or press F2.
In the logical system box, enter LG100.
Click on the save Icon
Click the back button.
Now select client 200.
Click details icon or press f2.
In logical Systems box, enter LG200.
Save
Back.
Comeback to SALE Transaction Code screen.
3) Maintain RFC Destination: (TR.CODE:SM59)
(Note: Do Not Create This Step)
Click Create Button on the Screen
On the Screen Maintain RFC Destination i.e LG200.
Enter LG200 in RFC destination box.
Connection type is 3
Give a description for the RFC destination.
Maintain Technical Settings on Details on Technical Settings tab
Target Host as : SAPKDC (NOTE: Save it as a Host Name)
Maintain Logon Details on Logon/Security tab.
Language: EN.
User:      MMUSER200 (This is the logon for dist.)
Client :      200
Password:      MM1234.
Save.
Click on create to do the above process for Client 200 in
The client 200 system.
4) Maintain Distribution Model.(BD64). (ABAPer role starts here)
Execute Maintain distribution model directly for
creating the model.
Click on change mode button on App tool bar of the Screen.
Create Model View pushbutton on App tool bar of the Screen.
A pop screen will appear in which you specify
Short text as Distribution for MM Data.
Enter Technical Name as LGMODEL.
Select Model View and Click on Add Message Type Pushbutton on App toolbar of the Screen.
A popup screen will appear in which you specify
Model View as      LGMODEL.
Sender as           LG100.
Receiver as      LG200.
Again Click on Add Message Type Pushbutton on App toolbar of the Screen.
A popup screen will appear in which you specify
Model View as      LGMODEL.
Sender as           LG200.
Receiver as      LG100.
SAVE.
On the same screen goto Menubar and select Environment.
And then select Generate Partner Profiles , then execute it.
On the Screen specify the Logical System as LG200.
Then execute the screen.
Click back.
Again On the same screen goto Menubar and select EDIT.
Again select Model View and then select Distribute.
****LOGIN to client 200.
Execute Tr.code BD64 and again On the same screen goto Menubar and select Environment.
And then select Generate Partner Profiles , then execute it.
On the Screen specify the Model View as LGMODEL
And Specify the Logical System as LG100.
Then execute the screen.
Click back.
*******Switch back to client 100 Session.
5) Create Material using MM03 Tr.Code.
Enter the material name as LGMATERIAL
Industry sector as      Mechanical Engineering
Material Type as           Finished Products.
And then Click on Data Pushbutton on the App tool bar.
Select views.
In the select views box for materials check basic data 1 AND 2.
Click enter icon.
In the next screen that you get
Give the text of the material as NEW MATERIAL.
Base unit of measure as KG.
Gross Weight as 200.
Net Weight as 100.
Weight Unit as KG.
In the description area language (E) and material description.
Click Save.
Now I Created a Material in Client 100 , I want to transfer this data to Client 200.
6) Execute BD10 to transfer the material in which you specify
the material as LGMATERIAL and
message type as MATMAS (client100).
Then a Screen will be displayed in which it shows that
1 Master Idoc Generated .. Enter
1 Communication Idoc Generated..Enter.
*******LOGIN to Client 200.
7) Execute BD11 to get the material in which you specify
the material as LGMATERIAL and
message type as MATMAS (client200).
8) Execute Tr.code MM03 and give the material as LGMATERIAL
and see that the material is displayed as it was in Client 100.
If not follow these steps.
9) Execute Tr.code WE19( for rectification of errors in client200).
Specify the Existing Idoc Number and Executes it .
A Screen is displayed in which you specify the corresponding Function Module as INPUT_IDOC_MATMAS01 and execute it.
10) Execute Tr.code MM03 and give the material as LGMATERIAL
and see that the material is displayed as it was in Client 100.
Now the Material is correctly displayed in Client 200.
11) Monitoring of IDOCS.
Transaction Codes:
IDOC Display of Status: WE 05.
IDOC Date and Time:   WE07.

IDoc problem after transpot

Hi all,
I have transported my XI scenario from Dev to Test (file transport), and now i have problems sending IDocs from R/3 to XI.
My questions is weather I have to reimport my "imported objects" (IDocs) ? It seams like thay altså have been transported, though - since they appear in my test system.
Thank you /Thomas

Thomas,
regarding to change objects: (delete...)
go to SWCV, where u have imported ur IDoc, dbl click to see namespaces. In the bottom, there is a checkbox - "objects are modifiable". Is it checked?
Why Idocs don't work?
Well, you moved the scenario objects, however, don't forget, that for IDoc communication there must be some settings done - partner profiles, ports, (standard ABAP AS settings for Idoc exchange)... If you moved just objects and didn't do this settings, of course, it won't work...
Peter
Message was edited by:
Peter Jarunek
Message was edited by:
Peter Jarunek

Frequent Idoc problem

Hi Guru's
We have a major problem on BW and APO. Sometime we have no extraction committed in BW or APO (All extractions of the night).
This is due to Idoc not comitted so to correct the problem we go In SAP R/3 source system transaction SM58 and "Execute in LUW". or after a few hours it commit all extractions itself.
But my problem is that this kind of problem appears once a week and i don't know why. SAP support can't help me because each time they connect, we committed manually or it was done automatically and they answer that they can't investigate.
Thanks for any idea.
Cyril

hi mate, have u checked that you are up to date with the latest firmware along with the latest Nokia system app updates from the Store? also try performing a soft reset, and check that your microSIM card is cut correctly etc.

MATMAS outboud Idoc: problem in SM58

Hi experts,
i have done Idoc to File scenario through SAP PI 7.0 server,
here SAP ECC 6.0 is the sender (MATMAS05- idoc) and Fileserver is the Receiver system and the SAP PI 7.0 is the Middleware system.
created Prtner profiles, customer distribution model view and distributed.
i triggered the IDOC from SAP ECC 6.0 system, (BD10), in WE05it is showing as IDoc processing success, data has sent to port and the status code is 03.
then i checked in tcode SM58, there it is showing under the
user - username
Function Module - IDOC_INBOUND_ASYNCHRONOUS
Target System - PI7CLNT001
Status Text - : : 000
can anybody tell me what would be the problem?
Thanks,
Kumar

Hi,
what kind of connection do you use between ECC and PI - RFC / Proxy? You can check this via SM59.
Is the file reaching PI or does the IDoc stuck in SM58? If it stucks in SM58 - try to reprocess it (hit F6 button).
Also what settings do you use in WE20 for partner PI7CLNT001?
Thanks,
Kai

IDOCs Problem

Similar Messages

Maybe you are looking for