Problem in idoc transportation

hi all,
i tried to create idoc and i have completed my idoc creation process till t-code we20.now when i go to t-code we60 and try to transport it then it is giving me error that ENTRY IN OUTBOUND TABLE NOT FOUND.
REGARDS,
VANEET THAKUR

Hi,
If u r using standard idoc then no need to transport .if u r using Zbasictype and segments then when u create it will ask for a transport request.So create a transport and attach ur segments and basic type and then release it to other system.
before releasing the transports,
u shud release the objects in their respective transactions from menu paths. this is very very important
If you want to transport include IDoc type and its segments in transport there is program RSEREPA3. You can check that program once......
to transport the message types...
Goto WE81 transaction in change mode.
Select the message types you want to transport.
Take the menu Table View -> Transport and give a transport request number.
may be this info useful for you...
-Thanks & Regards
Saurabh Goel

Similar Messages

Problem in Idoc creation in ME22N

Hi All,
We are facing a problem in Idoc creation in transaction ME22N.Our requirement is to trigger an output type and create a idoc everytime a change is made to a particular Purchase Order.
Presently however,for some vendors,when we change the plant at the item level,an Idoc is not created(with a message that the changes are not relevant to create an Idoc).Any other change to the Purchase Order like changes in quantity or price,results in successful Idoc creation.
We have also noticed that this happens only in the case of certain vendors.The Customer Info records and vendor data are all believed to be fine.
Are any other config settings required to be maintained for this?
Thanks in advance!
Regards,
Nejuma Iqbal

Hi Nejuma,
I don't think there is any problem with cofiguration settings.u r getting the idocs for some vendors .
if iam not wrong u r giving LS in the tcode(we20).The method which u r using is change pointers.As u r using standard idoc all the settings will be done.
Only settings u have to do is
1>generate partner profiles(WE20)
2>Distribute model view(BD64).
REGARDS,
Nagaraj

HR Programming : Problem with IDOC HRMD_A

Hello ,
We use Idoc HRMD_A for transferring PA records from
one R3 system (ECC5) to another R3 system (46d).
We have a problem - The Idoc doesn't check the data
inserted against the database check tables and
inserts wrong values into the target system database.
(At least that what has happened when we transferred
wrong value of MASSN in 0000 records).
Is there something we can do ?
Maybe - Some flag we can sign in order a check against check tables will be done ?
Is it a problem with this IDOC ?
Thanks .
I appreciate any help.
Nitzan S.

Consultancy note 134085 :
"Ultimately you are responsible for consistency of this data. SAP saves this data directly on the database without checking the single fields and consistency of the data records (time constraints check, writing change pointers, value check) because the consistency for an R/3 - R/3 lingage is of course ensured."
The IDOCs were intended for R3->R3 data replication, and not for data loads/interfacing. Since you're having problems, I'm guessing in addition they require the same SAP version as well.

Problem with IDoc scenario - IDocs do not aarive to XI

Hi guys!
I have a problem with IDoc->XI->File scenario. Colleagues send IDocs from R/3 and they are not in the XI. In R/3 they look like if they were correctly sent, however, I can not see them in sxmb monitor. BUT, when they send them again explicitly from R/3 (t-code WE19), they arrive...
REALLY strange...
Any suggestions?
IDX2 metadata loaded.. I think, all needed settings are done.
Question - do I need to set up LS in XI ABAP part?
Thanx, Olian!
P.

Hi Olian ,
just check if u have followed all the following steps
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2) a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name
Regards,
AshwinM

Problem sending IDOC DESADV /AFS/DELVRY03 to XI

Hi Gurus,
I have problems sending IDOCs DESADV (basic type /AFS/DELVRY03) created by function LSEND_IDOC to XI system. IDOC is correctly created by R3 system (AFS ECC 5.0) and correctly sent on the XI port (Status: Data passed to port OK - 03), but XI system doesn't receive IDOC.
If I resend the same IDOC by WE19 tcode goes ok!!
In R3 sending system nothing warnings/errors in syslog or sm58.
Any suggests? Thanks in advance.

Issue solved! It is necessary close the master idoc with a commit

Problem with idoc DEBMAS

Hi everybody.
We have a problem with idoc DEBMAS.
This idoc is sent from R3 to PI throw change pointers then the idoc is field only with the data modified in the master custumer.
We need the information fill it in the segment /IDOC/E1KNA1M/E1KNVVM to determine the receiver determination but this segment is not always sent.
What can be done in R3 to send always this segment.
We dont want to sent the whole data but always this segment.
Any idea???
Thanks a lot!!!!!

Hi,
As E1KNVVM segement is not mandatory, when you are triggering IDoc based on change poitner data might not populted in the E1KNVVM segment until some sales data is changed.
if you need that segement always just copy the Idoc type and make it mandaotry field.
otherwise yoy can populate some fields like STDVRS with the reruried constant and can use in your receiver determination.
Regards,
Suresh

Problem in Idoc type

Hi Experts,
I am facing one strange issue in idocs.
I am having a scenario where for particular LS i have assigned HRMD_A06 basic type and ZHRMD_A06 extension in partner profile.
and i am trying to implement badi HRALE00OUTBOUND_IDOC.
in this badi at runtime wrong message type is getting picked up at the runtime(checked in debugging). But at the end it displays proper basic type.
so for me it is getting difficult to write logic in this badi.
Please guide is there any particular setting apart from partner profile where we assign message type to LS.

Hi,
In problem in idoc type , that below link will helpful to you.
Try this link,
http://www.riyaz.net/blog/beginners-guide-to-ale-and-idocs-a-step-by-step-approach/technology/sap/18/
Regards,
Sekhar

Problem in IDOC generation

Hi Freinds,
I am facing some problem in IDOC creation . We have used MATMAS03 as basic type. And activated the chang poineter. But for some materials it is not generating IDOC.
When we saw table BDCPS with the change pointer number from BDCP it is showing some other Message type MATMASAD instead of MATMAS for the materials for wch IDOCS not sent. Can you please tell me where it is getting from this message type .

Hi,
      check with below mentioned tcodes.
      BD50 - This tcode for Activate Change Pointer for Msg Type.
      BD52 - Tcode for Activate change pointer per change.doc object or record.
    Goto BD52 -> enter the message type as 'matmas' and enter.so that u find the object type,table name and field name.
      The status of change pointer can easily be checked from   BDCPV table/view.

Problem when i transported DTP from DEV to QA

I am facing a problem when i transported DTP from DEV to QA It is not in the folder were it have to be,but i can see it in RSBKDTP table of QA

Hi,
One info regarding DTP, Technical name will get differ from system to system through out the landscape ( Dev, QA, Prod) . So you have to search with Description of the DTP instead of technical name.
Regards,
Sridevi.

Problems related to transport

Hi,
I have transport A and transport B.
A contains - CL_ABC and currently is under progress.
B conatins - test cases which are under class CL_ABC.
Now the problem is I have released B and I am still working on CL_ABC which is under transport A.
Will it create a problem? What can be the resolution? Or when I release transport A, work done under B will also work fine???
Please help.
Regards,
Arpit

Hi Arpit Goyal,
Generally you should transport firstly A and then B because B contains some test cases regarding to A. But you trabsported firstly B right? .. No problem you can transport A, after transporting this request A your program will be workig fine.
Note : Program is not generated when you released the request B, you should release A also. After relese this your program will be working fine.
Regards,
Mahi.

FIle Content Conversion Problem in IDOC-XI-File Scenario

Dear All,
I am doing IDOC-XI-FILE scenario.
I am facing one problem related to File Content Coversion.My requirement was to generate a dynamic file like %store_code%_%current_date%_sitemaster.xml , I have completed the dynamic generation successfully .
Now there is slight change in the requirement ,we have to suppress the current_date node of the xml content . i have tried to suppress the current_date using these DATE.fieldFixedLengths 0 , Date.fixedLengthTooShortHandling Cut , But I am unable to suppress it Can some body provide me the details on this .
The output xml version generated by Reciever file adapter is as below :
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:MT_SITE_MASTER xmlns:ns0="http://sample-xitest.com/sitemaster">
- <SITE_DATA>
<STORE_CODE>N002</STORE_CODE>
<TITLE_MEDI>Company</TITLE_MEDI>
<STORE_NAME>Mount Road</STORE_NAME>
<STREET>Chennai</STREET>
<COUNTRY>IN</COUNTRY>
<SALES_TAX_NO>12345678910</SALES_TAX_NO>
</SITE_DATA>
</ns0:MT_SITE_MASTER>
Plz provide me the code I have to write in the file content conversion .
Thanks in advance
Regards
Prabhat

If u see my earlier reply, I mentioned that u can not suppress the field from the one node.i.e Form SITE_DATA data type u can not suppress the field called CURRENT_DATE.
My suggestion is that , modify the Data type in such a way that you will be having two nodes as I have mentioned earlier. Then use the Suppress Logic for the Current Date.
So it will look like this-
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:MT_SITE_MASTER xmlns:ns0="http://sample-xitest.com/sitemaster">
- <SITE_DATA>
<STORE_CODE>N002</STORE_CODE>
<TITLE_MEDI>Company</TITLE_MEDI>
<STORE_NAME>Mount Road</STORE_NAME>
<STREET>Chennai</STREET>
<COUNTRY>IN</COUNTRY>
<SALES_TAX_NO>12345678910</SALES_TAX_NO>
</SITE_DATA>
<CURR_DATE>
<CURRENT_DATE>20051105</CURRENT_DATE>
</CURR_DATE>
</ns0:MT_SITE_MASTER>
So ur SITE_DATA is not having a field called CURRENT_DATE. This field is in separate node (segment ) called CURR_DATE. Now u can use the Suppress Logic for the same like this.
CURR_DATE.fieldFixedLengths - 0
CURR_DATE.fixedLengthTooShortHanling - Cut
And in your Variable Substitution you can use the date from the other segment called CURR_DATE.
Hope this solves ur problem.
Regards,
Moorthy

Problem with IDoc for an outbound delivery

Dear All,
I am facing a problem with the IDoc defined for an outbound delivery.
Scenario:
Implementation of a small enhancement for an IDoc (DESADV, DELVRY01) created for an outbound delivery (in VL02N).
What I did:
I implemented the EXIT_SAPLV56K_002 exit in the V56K0001 enhancement, activated in SMOD, assigned V56K0001 component in CMOD and acivated it. Then I put a breakpoint on the ZXTRKU02 include. For me everything in SMOD and CMOD looks OK.
I have also created a partner profile, port, outbound message config. (message DESADV, basic type DELVRY01, application V2, output message type LAVA, process code DELV. function module used for this process code is IDOC_OUTPUT_DELVRY).
What I can do:
I can issue an IDoc message, it looks ok and contains the standard data.
Problem:
It seems that the enhancement does not work. Finally I put there only one line of code to avoid a program bug and just to check . The system does not stop at the breakpoint (set on the ZXTRKU02 include in the EXIT_SAPLV56K_002 exit).
Am I using the proper exit? I appreciate any suggestions.
Thanks,
Grzegorz Skorus

Hello Grzegorz
Not an expert on this, but noone is responding so I thought let me try and help you. You seem to be doing the right things as mentioned in OSS note 1498409.
Firstly since this can be called form Shipment Idoc also, you may need to make a differentiation by the interface parameter 'MESSAGE_TYPE' or segment name. See the attached OSS note, though it belongs to older releases, it may help you.
Also help says 'The callup of this function module is programmed for each enhancement of the internal table for the IDoc (in other words, when you add an extra segment'. So may be you need to add an extra segment/field to make it work.
Futher the user exits are replaced by BADIs. May be you should use exit_badi_v56k.
Hope this helps and others will pitch in.
1498409 - Valuation Type unavailable when creating deliveries using IDOC
631913 - Exit after formatting delivery IDoc type DELVRY

Problems with idoc ORDERS05

Hi experts,
I created a new Z segment for idoc ORDERS05 and it works fine. This idoc is generated whenever a PO is created or modified. But if the PO has locked or deleted items, there is no segment for this items in the IDOC. Should I modify any code or something in SPRO??
Thanks in advance,
Maria

Hi again...
I'm trying to make a copy of the standr FM IDOC_OUTPUT_ORDERS because I think it may be easier to add the segments I need. I have also created in tx. WE41a new operation code ZME10 with my new fm. An in tx. WE20 I have assigned ZME10.
The problem is when I run ME9F i get this error:
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_DYN_CALL_ILLEGAL_FUNC',
was neither
caught nor passed along using a RAISING clause, in the procedure
"NEW_DYN_PERFORM" "(FORM)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
The program "RSNASTED" contains the CALL FUNCTION statement.
The name of the function module to be called is "ZIDOC_OUTPUT_ORDERS".
but "ZIDOC_OUTPUT_ORDERS" cannot be found in its function group.
Any idea ??
thanks in advance !

PROBLEM IN RELEASING TRANSPORT REQUEST THROUGH SE10

Dear all,
I am trying to release transport request of development server via. transaction se10.Now my problem is that the child(DEVELOPMENT/CORRECTION) is getting released while the parent request is not getting released.
I checked everything and its showing 'test call of transport control program ended with return code 0208.' I even checked overview of system,overview of connection type,over view of transport protocol and they are fine.my only doubt is after going to se10 when I click transport proposals its showing "WORK FLOW NOT ACTIVE' .
Is my problem is because of this. Please help its very urgent as due to this I am not even able to transport any request on production server.
Helpful contribution will be duly rewarded.
Thanks & Regards,
VICKY

hi
vicky just went through your Query regarding release
of requests..first of all U be sure of TMS configuration
see whether it is consistent or not.then after Refresh
the system and then come to release of requests.
its true that we can transport through scc1 but first
check about STMS configuration and the way you set
that.
Regards
manjula.

Problem with SPAU Transports after Upgrade and after applying SAPKW70016

Dear All,
we copied old dev to new QA, upgraded new QA, then copied new QA to new DEV.
did the SPAU adjustments in DEV. At that time DEV SAP_BW version was SAPKW70015. After that we applied SAPKW70016. Now we're having problems with the SPAU transport because of the application of SAPKW70016.
Requested to kindly suggest ASAP.
Thanks & Regards
janardhan Kumar K

Hi,
Could you please to be more specific with the error ? Please check the log e send us the message error that is happening during the transport.
Thanks,
Walter Oliveira.

Problem in idoc transportation

Similar Messages

Maybe you are looking for