IDoc Set Release

Hi All,
1. I have created Segment in WE31, Basic type in WE30. If I do (Edit -> Set Release) then can I add new fields later on into that segment and in effect will it be included in Basic type?
2. I have created Message type in WE81 and attached it with Basic type in WE82. What need to be given in 'Extension' field. Please explain with details as I didn't understand after pressing 'F4' there.
3. For Outbound IDoc I need to write a Report(with 'MASTER_IDOC_DISTRIBUTE' function module) or only Function Module will serve the purpose?
a. If Function Module then, please specify will it be a RFC enabled Function Module (BAPI) or simple (without RFC)? Please provide the code if possible.
Thanks & Regards,
Anindita

1. No, once u set release u canu2019t add fields later and it will not effect basic type.
2. It is optional. Combined with an IDoc type from the SAP standard version (a basic type) to create a new, upwardly-compatible IDoc type.
IDoc processing:
     If an EDI subsystem is used, the subsystem should not modify the field CIMTYP.
     1   Outbound IDocs: the application selection module maintains the field CIMTYP from the field PARTOUT (partner profile).
     2   Inbound IDocs: the IDoc Interface checks whether the specified extension exists in combination with the specified basic type.
3. Yes use FM. According to ur scenario u want to choose BAPI or simple RFC

Similar Messages

EDI/IDOC setting

Hi,
Can anybody suggest regarding any EDI/IDOC setting for SD counsultant apart from developer's work?
Regards
Susrikant

Apart from output there is nothing in SPRO, but there is lot to be done in WEDI.
To understand the basic configuration adn teh setup reqmt for IDOCs, EDI, you can go through the following links.
Then you will understand the configurations needed.
http://www.riyaz.net/blog/index.php/2008/01/19/beginners-guide-to-ale-and-idocs-a-step-by-step-approach/
http://www.scribd.com/doc/24447/SAP-R3-IDoc-Cookbook-for-EDI-and-Interfaces-by-Axel-Angeli
This one is really good, try to complete the book
http://www.thespot4sap.com/Articles/SAP_ALE_IDOCS.asp
Hope this helps.
You can reward if this helps you

Ale/idoc setting

Please use more informative subjects in future. How are we supposed to differentiate between your questions when you keep using the same subject?
hi folks
i am working on outboung idoc...here in the settings part when i created a port and gave the port name in the partnerprofile its giving the message please enter a value for package size.
could someone let me know exact way of setting the configuration....
i am working on sending vendor data i.e. message type is cremas...i hv extended this.
thanks in advance
Edited by: Matt on Mar 23, 2009 2:13 PM

you can find the below example of idoc setting for out bound
A. First of all, we need to identify the Transaction Data which is required to be Transfered to external System.(Ex: Sales Order Data or Shipment Data or Delivery Related Data).
B. Secondly, Identify the IDoc Type & Message Type. IDoc Type can be found in Transaction WE30 & Message Type Can be explored in Transaction WE81.
C. After that, assign the IDoc Type to Message Type in WE82.
D. Identify the Selection Program (Outbound) which is generally a Function Module in the Form of IDOC_OUTPUT_<Message Type>. Example, if the Message Type is ORDERS, the FM will be IDOC_OUTPUT_ORDERS.
E. Assign the Function Module to a Process Code in WE41 (Process Code for Outbound).
F. Configure Port Definitions in WE21 for which the RFC destinations are to be maintained in Transaction SM59.
G. Maintain Partner Profiles for the Outbound Message Processing in WE20.
H. Last, but not the Least, we need to Focus Mainly on Message Control Configuration which is nothing but maintaining the Output Type for the Outbound IDoc to be Triggered for the Sales Order Application or Delivery Application.
i. In Message Control Configuration, we'll maintain
1. Condition Tables
2. Access Sequences
3. Output Types
ii. To Create the above elements, we can go to SPRO Transaction and do the same depending on the Application Area such as Sales / Shipping / Logistics Execution etc.
iii. For Output Types & Access Sequences, we can go to the Transaction NACE or VK01 in which we'll maintain the Output Types / Access Sequences & Condition Records.
Please note that all the above steps may not be needed if we are using some of the Standard Elements provided by SAP such as Message Type, Process Code, IDoc Type & Selection Program as many of the Standard SAP Applications have their own Elements for different Application Areas.
For example, if you want to send an Order Confirmation IDoc when the Sales Order is saved, you can use the Message Type ORDRSP, IDoc Type ORDERS05 & Selection Program as IDOC_OUTPUT_ORDRSP.

Patch Set Release 2 (9.2.0.8) Patch Set 7 for Microsoft Windows (32-Bit)

Hi,
I've 2 nodes with version 9.2.0.1
I applied a Patch Set Release 2 (9.2.0.8) Patch Set 7 for Microsoft Windows (32-Bit) on the Node 2,
All is fine but when i try to discover N2 from N1 with OMS, i get only the HTTP Servers, and no database discovred,
For your information, I've 2 databases on N2
Please help me to resolve this probleme because i need to schedule some jobs.
Regards.

Check where you installed the 9.2.0.8 patch, in the database home or Enterprise Manager Agent's home?
Check the compatibility between the versions of agent, database and OEM.
Try to reinstall the (correct version) agent again in Node 1.
If you have 2 database on Node 2, if they both uses the same Oracle database version and same home, you need to install the patch only once, but got to run the upgrade and catpatch.sql seperately in each databases.
Hope it helps,
Babu Rangasamy

How to release PRs through workflows without setting release procedures?

Dear all,
         I am involved in overall purchase requisition workflow.I have copied standard workflow WS20000077.
         For overall PR release,I will be using the standard task TS20000159 which uses BOR as BUS2105 and method SINGLERELEASE.This method is defined with RELEASECODE as mandatory parameter.
         My functional consultant wants me to get release codes from ztable based on plant and PR value without setting release groups and release code in SPRO transaction.
         So,I have created an entry in ztable for release code with data element FRGCO as in T16FC standard table with SAP log on id of agent ,plant and PR values.I have created a custom background method to pick the appropriate release code from ztable based on PR value and plant.The picked release code now can be passed to he above standard task.Is this a right procedure for PR release?Please correct me if I am wrong ,as this is the first time I am involved in release workflows, for which I will be grateful.
Thanks and regards,
S.Suresh

Dear Swaminathan,
                 Thank you so much for your reply.
                 I will get back shortly once this is done.
Thanks and regards,
S.Suresh

Extraction failure and then picked up due to IDOC setting on source system

hi All,
Just give one master data Company Code load as an example. We run the data load every night around 12 though Process Chain. When we checked the monitor, find that it ran twice, 1st time, it ran at 12 which was supposed to run, but it failed with red error and the red error msg is:
"IDocs were found in the ALE inbox for Source System that are not updated. Processing is overdue."
then it ran again at 07:45:55 which was successful with green light. We guess this problem is caused by IDOC setting on the source system. Run WE02 on the source system, expend Inbound IDocs folder and then expend RSRQST folder, find status 64 which indicates the yellow status.
Can anyone explain here why the extraction failed 1st time around 12am due to IDOC setting on the source system, and then the run was picked up around 7am successfully?
Thanks in advance!

Hi Kevin,
this is really a strange behaviour. What I could imagine: it could be temporary network issue or performance issue or system unavailability on the r/3 source system side. maybe you could check if other processes/jobs on R/3 were canceled, or if there is any system log available at the time concerned.
Lilly

Setting release mode

I am using jdev10g. I want to set release mode property of an application module to Statless after log out. Where can I do that? I have tried with struts-config.xml, like this:
<action path="/aziendaLogout" className="oracle.adf.controller.struts.actions.DataActionMapping" type="sicuro6.view.AziendaLogoutAction" name="DataForm">
<set-property property="modelReference" value="aziendaLogoutUIModel"/>
<set-property property="releasemode" value="Stateless"/>
<forward path="/aziendaLogout.jsp" name="success"/>
</action>
But it doesn't work.
Does this code make sense?
public class AziendaLogoutAction extends DataAction
protected ActionForward findForward(DataActionContext actionContext) throws IOException, ServletException
AziendaBrowseS6ModuleImpl sicuro = (AziendaBrowseS6ModuleImpl) actionContext.getBindingContainer().getApplicationModule();
sicuro.setProperty("relesemode", "Stateless");
// TODO: Override this oracle.adf.controller.struts.actions.DataAction method
return super.findForward(actionContext);

According to this posting (Re: How do I set Stateful/Stateless behavior in 9.0.5 stateless releasemode is not supported in the 10g (=9.0.5) preview.

Set Release Level of IDoc Extension

I'm currently in the middle of an upgrade from 4.7 to 6.0. We're having an issue with IDoc INVOIC01, which has an extension called ZINVOIC01. The extension only has one segment with only one definition version, but the release was never set. Now I want to set the segment release level for the Idoc in the partner profile to 46B, but it errors out because of the extension. If I try to set the release on the extension now on 4.7 it goes to 620 and on 6.0 it goes to 701. Is there a way around this? Can I set the release to 46B in the extension somehow?
Thanks All,
Clint

Hi Sandra,
Thank you for the response! Let me try to explain from another angle. Here is the error message on the outbound IDoc after upgrade and partner profile config change: "Segment Z1EDP19 is unknown in Release 46B" (Status record 02 -Error passing data to port). The reason is because the IDoc extension to this segment was never released. The reason I'm trying to use release 46B is I want the same IDoc we had under 4.7. I'm specifing the release in the partner profile. If you don't specify a release in the partner profile you always get the newest release. Here is the segment definition for the standard segment:
008     E2EDP01008     700     603     52     543     08/24/2007
007     E2EDP01007     620                    51     542     10/15/2004
006     E2EDP01006     46B                    48     460     05/03/2000<--- I want this one!
005     E2EDP01005     46A                    47     438     03/16/1999
Hope this helps explain.
Thanks again,
Clint

External kanban- JIT Idoc set to vendor.

Hello
I am setting the partner profile for the JIT Call in KANBAN for External Procurement.
I have defined as follow:
Partner number 6722334
Partner type: LI
Partner function: OA
Message type: PAB_ORDERS (Quantity release from KANBAN)
Outbound option tab:
Receiver port: SAPDEV
Transfer IDOC immed:
Output mode: 2
Basic type: SEQJIT01 (JIT: IDoc for sequenced/summarized JIT calls)
Message Control Tab:
Application PA :JIT call
Message type: ZDKA-JIT Call EDI
Process code: PJN0 (Generation/export of IDOC orders03 for JIT call)
When I am checking Idoc in ME38 under messages it is showing red
the status process is in error, and the error is below:
No corresponding entry in table JITOIT Message no. JIT00017
I check the table JITOIT and it is empty.
Did I miss some in configuration? Or how that table is to be filled?
Rgs
Edited by: sudhir.R.T T on Nov 25, 2011 12:53 PM

Hi Sagar
For the Confirmation you need to do the customizing for confirmation control, like what would you like to do after the confirmation. Confirmation is an inbound process.
For Invoice you need to complete the customizing under LIV in SPRO- for Invoices received via EDI.
Please go throught the help link for further details.
http://help.sap.com/saphelp_47x200/helpdata/en/a8/b99f58452b11d189430000e829fbbd/frameset.htm
Reward points if useful
Thanks & regards
Kishore

IDOC Segement Release vs IDOC Basic Type

Hi there,
we are in an upgrade project and are runing into a general question about idoc creation.
Here is our behavior:
1. We have an reduced IDOC Type in BD53 ZMATMAS based on Messagetype MATMASDI.
2. It has 2 Segements E1MARAM with fields MSGFN MATNR PSTAT and Subsegemnt E1MAKTM with fields MSGFN SPRAS MAKTX.
3. Done the things around (RFC, Partner Profile, distribution model, changepointer ..)
4. In Distribution Model in outbound parameters, added our ZMATMAS.
As parameters we have: Partner type: LS, Message Type: ZMATMAS, Basic Type MATMAS03! and Seg. release in IDOC Type 46B. The Partnersystem is an NoneSAP System.
We are using MATMAS03 because this interface exists since 46B.
Now we send an Material with BD10 and Message Type ZMATMAS.
The Master and Commuidoc are successfull created. In BD87 the commuidoc is an MATMAS03 and has the expected 2 segements E1MARAM and E1MAKTM.
But what we do not expect, if we look into the content of E1MARAM there are ALL Fields which exist for the E1MARAM in release 7.00. Not only our 3 fields MSGFN MATNR PSTAT, or as we second expect only the segemnts that had existed in the segemnt E1MARAM in release 46B of MATMAS03.
The additional fields were filled with the NODATA sign.
My question is: Is it correct that an IDOC with basic type MATMAS03 can have an segement E1MARAM which is formated like the segemntdefinition E2MARAM007 (Release 7.00 / 6.03)?
The difference is definatly the length of the field! 876 in 7.0 vs 757 in 4.6A.
Why is SAP using the highest available segemnt release regardles which basic type we choose?
Isnt this wrong?
Additional infos:
We know that it is not possible to have an IDOC with basic type MATMAS03 with an segement e.g. E1MARA1 which only exists in newer basic type MATMADI if segemnt release is set to 46B in our distribution model.
Failure is: Segment E1MARA1 is unknown in Release 46B/ (correct and expected behavior)
If we are using this scenario with not an reduced message type, we will only find the fields in E1MARAM which are filled with data. (Not all fields of the latest release with nodata)
I traced the MASTER_IDOC_CREATE_MATMAS and hit the function IDOC_REDUCTION_FIELD_REDUCE. As you can see in it, it first checks if the idoc is an reduced message type, and at the end, fills up all fields with the "empty_symbol" which have no data in it. Why is this only happening if it is an reduced message type?
Kind regards
Manuel

Additional Info:
In WE21 at the TRFC Port, it is possible to set this Option:
Send Only Fields of Selected Segment Version
The segment data of the IDoc is passed to this port with the length matching the segment definition of the release specified in the partner profile.
But if we are using an reduced message type, all fields of the newest release are in the segement.
The docu tells that this will be done in function EDI_DOCUMENT_OPEN_FOR_CREATE.
But it is never called when createing an material IDOC with BD10.
Bug or feature?
Kind regards
Manuel

Outbound IDoc setting through ACC_GL_POSTING

Dear Members,
I am willing to post an IDOC ( Msg type : ACC_GL_POSTING or any other) for FI Transaction G/L Posting without using any user exits. Is there any way to post it with standard setting???
Thanks in advance,
Audy.

Hi Karun,
Actually, I was trying to create an IDoc'ACC_GL_POSTING' for certain G/L postings without using MASTER_IDOC_DISTRIBUTE function explicitely ; but finally got configuration for cross-system company code setting in SALE transaction. This can create IDoc FIDCC01 or FIDCC02 whenever an FI doc. is posted. We just need to create a partner profile for it...
Is there any other setting which can generate IDoc ACC_GL_POSTING in similler way??...Like using some SPRO setting??
Also while posting same IDOC i.e. 'ACC_GL_POSTING' using standard process code 'BAPI' , we need many conversions , custom checks etc....
My problem is, Which is better way?? write a big code in exit of posting program or write separate Z-posting program tio post IDoc..
Thanks and regards,
Audy.

10.1.0.5 Patch Set Release Date?

Hello,
Does anyone know the projected release date of the 10.1.0.5 patch set for Oracle Database Server?
I'm interested in Solaris SPARC patch set.
Thanks,
Vlad

CPUJan06 states that 10.1.0.5 is supposed to be release today Jan 31, 2006.
Though it is still not available via metalink...

IDOC setting for tcode PB40 and applicant creation

In tcode PB40 (a tcode of HR Module), when for example, Applicant Creation is done, an IDOC is triggered.
We are encountering an error in the IDOC which is trigered when Applicant Creation is done because that IDOC is picking up a partner profile which is not correct.
Please tell me where is the setting maintained which dictates the triggering of IDOC in tcodes like PB40 (so that i can debug why is it picking up a wrong partner profile)

Hi,
This output determination is done using NACE..
For your scenario in We20 check the message type you are using and associated partner profile...there you need to configure the message control for generation of the idoc check whether this has been configured in different partner profile than required..
Also check any distribution model associated for this data (Tcode :BD64)
HTH
Rajesh

Idoc segment release

Hi,
I wish to change one of the field's length in an idoc segment. It doesn't allow me to change it as the version is already released.
However, I cannot cancel the release too, as the released version belongs to an earlier version of SAP (4.7).
The current/existing version of the segment is of release 620. The current release is 710, so no change seems to be possible.
I can't create another version too, as it doesn't allow change of the earlier field definitions.
Could someone pls help.
Thanks!
Arthi

Hi,
We have similar issue. In the ORDERS05 IDOC, we had made changes to the segment E1EDP19 to repeat 99 times. Then IDOC extension ZORDERS05 was created. Due to new enhancement pack, the attributes of E1EDP19 were changed to repeat 5 times as per standard SAP.
This did not work for us because segment E1EDP19 should repeat 99 times. So we ran program to update the attributes of this segment. Now E1EDP19 can repeat 99 times.
But when we are processing ZORDERS05, the chagnes are not reflected. The reason could be, even though E1EDP19 was changed, it will not reflect in IDOC extension. For this to reflect, we are trying to cancel release ZORDERS05 once and release again.
I am not able to do this activity. Any pointers to this will be helpful. My requirement is to just cancel release once and release it again. Also while doing so, SAP message pointed me to 844899.
Regards,
Shahu

Inbound Idoc set up..

Hi All..
Iam using the following bapi " BAPI_SALESORDER_CREATEFROMDAT2" to create credit/debit memo requests in sap. If the bapi fails, i want to create an idoc and post the application document.
For that purpose, iam using the idoc type SALESORDER_CREATEFROMDAT2 which has the same strucutures as needed for the above bapi. Since the existing message type SALESORDER_CREATEFROMDAT2 is used for other purpose, for my scenarion iam creating a zmessage type. Iam also copying the FM: IDOC_INPUT_SALESORDER_CREATEFR to Z functionmodule to remove the hardcoded value for business object. Iam also creating my own process code.
In this scenario.. iam getting a flat file to SAP. Iam reading the flat file into internal tables and creating the needed internal table for the bapi structurres and passing them to the bapi to create credit/debit memo request. Whenever the bapi fails, i have to pass those structures to the IDoc type to create and idoc and after creation of idoc, it should try to post the application document using the Zfunctionmodule above.
Can you please let me know what are all the settings needed for this Idoc configuration. Also in this case do we need partner profile set up or not.. Where can we set up all those process code, FM, message types etc..
Appreciate your help..

Please refer this thread, it might help:
IDoc FM

IDoc Set Release

Similar Messages

Maybe you are looking for