Cancel release in idoc

Hi Friends,
We are upgrading our ECC system from release 700 to 731. For one of the idoc interface we are using SHPMNT03 idoc. Post upgrade it is observed that E1EDT37 segment version is updated from 003 to 004. Biz Talk(middle ware), whose schema is desinged for old version of idoc(700) is unable to post idocs to SAP. Is there any way I can revert the version of this standard segment. While following the path EDIT->CANCEL RELEASE in WE31 for this segment I received an error - "Name range violation : Name E1EDT37 not permitted in CUSTOMER system".
old system
lo
new system.
Please let me know your thoughts.

Thanks for the response Vadamalai.
You are suggesting to enhance the code at coding level. Can you please eloborate me more on that. Inbound idoc is not coming to reaching to SAP itself. We are not sure at which level check is happening.
One more thing is if we create custom idoc with z segments, will these z segments also get updated( change in release) while doing next upgrade.
Thanks,
Gowrinath.

Similar Messages

Idoc Segment Cancel release error

Hi all,
I have problem in cancelling the release of an Idoc Segment. I have a requirement to add new fields to the segment. When I try to do Edit->Cancel Release it is throwing below error.
"Error while resetting release of segment Z1PXXXX
Message no. EA259"
Could anyone tell me how to overcome this error or the root cause of this error?
Many Thanks,
Sri
Edited by: Arunsri on Nov 10, 2009 8:37 AM

Hello,
The reason that you are getting these errors is that you cannot cancel
the release of an extension made in previous version e.g. 4.6C. Instead you have to
create a new extension.
It is not possible to change a segment definition which is released in a
lower release. This is a basic concept of our release strategy to
guarantee compatibility between different releases.
You must create a new segment definition for the new release e.g. 620 with a new segment
field with the appropriate length. In transaction WE20, outbound parameters, you can specify
the "segment release in IDoc type" for the communication. Please read the F1 help of this field for further
information.
For your own segments you can define a new version of the segment via
transaction WE31 -> Add Version (Shift+F5).
Please review your online help for more information on this and related topics.
Hope this information helps.
Regards,
David

Unable to cancel release of an IDOC

Hi All,
I am trying to cancel release of an IDOC that I developed in 4.6C environment. We are now on ECC6 environment and when I try to cancel release it gives me an error "Can not unclose segment: release of last version is not SAP-version". Has anyone ever experienced it? How can I resolve it?
Thanks for your help.
Regards.

Hi,
Do you remember how you did it?
Many Thanks!

Internal Order Release/Cancel Release/...

Dear All,
I have several questions regarding Internal Order (Order type - 0401) release/cancel release options.
In order to make IO "usable" After creation I select Release option and then assign the budget to the order. When the order is no longer needed I choose Cancel release so the order can be no longer used.
So I am interested in:
1) I have lots of orders which must be cancelled, is there any trasnaction for Batch canceling or releasing the orders?
2) Does canceling the order affect for example expenses posted on this order? I mean expenses posted on this order dissapear or stay as it is?
3) what is the difference between Cancel release and Technically completed.
Thank you in advance.

Hi,
Yes CLOSE is the right option for finishing the order. As per my understanding there is no option in standard system to mass cancel/release an order.

PO Cancel release problem

Hi, experts:
I am a beginer of SAP workflow, I've got a problem when testing customized PO cancel release workflow.
My workflow is quite simple, just test whether the event 'SIGNIFICANTLYCHANGED' was trigered when cancel PO. I will receive information in my SAP Business workplace.
Here is the configuration of PO release Strategies:
RGroup Rcode Workflow Agent
PO     C1     1     Blank
PO     C2     1     Blank
PO     C3     1     Blank
PO     C4     1     Blank
In my customized workflow template, I use the event 'SIGNIFICANTLYCHANGED' to deal with PO cancel release.
But I find that this event will not be triggered from Level C4 cancel to C3.
Here is my test result:
Cancel        Result
C4->C3       Not triggered
C3->C2       Trigered
C2->C1       Trigered
I can get the result from my Business workplace except cancel PO from C4 to C3.
Does anyone come across with this problem?
Please tell me why and how to handle it, thanks a lot!
Best regards!

Hi,Swaminathan PJ
Appreciate for your reply!
So, shall we change another event or even customize our own event?
My requirement is that send e-mail with PO item detail (*.xls file) to specified users when final release or cancel final release.
Thank you for any good advice.
Best regards!

PO Cancel Release and Rejection

Hi,
Can anyone point me to any documentation on Cancelling of Release in a PO and the Rejection button in the PO? What are the differences and how can I disable the cancelling of release functionality?
Thank you.

Cancell Release - After release /output if you want change the PO value .possible only in ME28
Rejection - If the approver does not satisfy with conditions he can reject the PO - possible only in ME29N

Cancel release of Contract

Dear Experts,
I am using std workflow WS20000079 forcontract release. I have a scenario where user can cancel contract release. From SWEL i found that SIGNIFICATLY CHANGED, RELEASE STEP CREATED events are triggered when cancellation of release occurs. In outcome Contract changed significantly of step 00047 (in WS20000079) i have included a activity step. There i have included a custom method in task step. When i cancel release i see that status of workflow is In process and does not become completed. Can you please tell me why the status is In Process.
KR,
S Bharath

Hi,
In these kind of scenarios please use fork and wait event.
In your fork one branch should have the normal flow and in another branch,
please use wait for an event for cancel and once it occurs , do complete the workflow.
Thanks and Regards,
Swaminathan

Cancel Release

Hi,
I cannot cancel my release strategy(ME29N), once I click icon for cancel release the system prompt me this message:
"Document has already been outputted (function not possible)". So I've try to change PO but system message dipslay:
"Purchasing document has release indicator S (changes not possible)"
Can anybody help me on how to change the config.?

Hi
I think we have some solution workarounds..
1) Try this. Go to Me23n->Messages ->Repeat Output; You have a new message created; Ensure that the output option is 'output in a separate Txn' in 'Further data'.
Now goto ME28 and try to cancel this PO. This trick works in some versions of R/3.
2) If the above option fails...you need some ABAP help. Copy the ME28 program and create a new z-program and Ztxn (ZME28). In this program, there is a check for whether 'document was output'; just comment that check and you can cancel the release after output also.
Best regards
Ramki

Cannot cancel release stratigy after output is printed

Dear Expert,
I has been configuration output for PO ( print auto after release stratigy)
After I release stratigy there is a scenario that user need to cancel release stratigy
But the system is error not allow to cancel release stratigy after output is printed
What's I miss? thank you very much.
I release stratigy using ME29N and cancel using ME29N and ME28 also.
Best regards,
@tom _

HI,
In ME9F itself try to repeat the output.
Thanks & Regards,
Kiran

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

Authorization for Cancel Release

Dear Expert,
Does anyone know what is authorization object to restrict cancel release? Because now if there is 3 level release (ex: E1, E2 and E3) and status release PR already final (E3), user level E1 still can cancel release status in PR and all release status will reset even if follow up document such as PO already created for that PR.
Any solution for this??Really need ur help....
Thank You,
Aleluya.

The auth object is M_EINK_FRG
But, That checks only release code. Not the activity ( Release or Reject)
May be EXIT_SAPLEBND_001 is use ful to control
Regards,
Dev.

Error Cancelling Release of Basic Type

Hi,
Im using WE30 to make changes to a BASIC type. So in the menu EDIT->Cancel Release an error prompted these messages:
The release of the basis types cannot be reset
Message no. EA506
Diagnosis
The release can only be reset if the basis type has been released in the current Release. Basis type ZPADET01 has already been released in Release 46C, so this release can no longer be removed.
Procedure
Create a successor to basis type ZPADET01 so this new basis type can be further developed.
I usually modify BASIC type with WE30 successfully. But this error message I'm at a lost.
Please Help,
Sid

i wouldn't go about and delete it. just create a new one, let's say YPADET01. when you clicked the button 'create' there comes a pop-up where you can decide how to proceed. it is there where you can decide whether you want the new one to be a successor of ZPADET01.
actually, i have been doing some reading on the subject and found about that release-thing:
http://help.sap.com/saphelp_erp2004/helpdata/DE/dc/6b832543d711d1893e0000e8323c4f/frameset.htm
start there and dig a bit around, so you can get a better clue on how to go on.
sorry, that was the german link, here you go in english:
http://help.sap.com/saphelp_erp2004/helpdata/EN/dc/6b832543d711d1893e0000e8323c4f/frameset.htm
Edited by: Mylene Euridice Dorias on Aug 11, 2009 8:13 AM

How to release the IDOC based on the count

Hi IDOC gurus,
How to release IDOC's based on the count?
Actually, my requirement is I have to release the IDOC's of count 50 for every 5 or 10 minutes. I tried by scheduling the background job for the program RSEOUT00, but unfortunately there was no option of selecting the IDOC's based on count for the given message type except IDOC range i.e FROM and TO select options in the selection screen.
Are there any other alternative where I can release the IDOC's based on count for every periodic 5 or 10minutes?
Also, can I know how can we configure the multiple QUEUES for the IDOC's?
I highly appreciate who can help regarding this and points are awarded.
Thanks,
Sreevani.

Hi Ferry,
I tried with that option. Maximum number of IDocs parameter is the package size not the count of IDOC's.
I have 100 IDOC's with status 30 and all IDOC's got released eventhough the value of "Maximum number of IDocs" parameter is 50. I checked in the code it is an package size i.e., maxm IDOCs that it can be transferred from RFC outbound queue to a port at time and not maximum number that can be processed for the program execution.
Thanks,
Sreevani.

How to cancel release of a transport in "release started" state.

Hi All,
I had released a tranport and the tranport is stuck in "Release Started" phase due to issues with one of the objects in the request.
I believe we can fix this by modifying the object. But for that either the transport has to be fully released or it has to be out of "release started" phase.
Can anyone please advise as to how do we cancel release of a transport which is in "Release Started" phase?
Thanks,
Tirth

Transaction SE03 offers option "Unlock Objects (Expert tool)", which has a checkbox "set to released".
You can give this a try, but you should better contact a system administrator ("basis") beforehand, as this is not an ABAP development issue.
Thomas

Remove cancel release button

Hi, is it possible to remove the cancel release button in the PO Release Tab? We would like to restrict the PO from being edited. We already set it in the system messages, however, the users tend to ask the releasers to Unrelease the PO for them to edit the PO. Appreciate your help..
Thanks!
Paula

Hi,
All seems very ok,
But there is a scenario:
1.PO creator creates an PO,and then he should release the creator-level through ME29N.
2.The manager also released the PO.
3.The creator found that he should edit the PO,as your plan setting the changability to provent against editing.
4.The creator still can edit PO after cancelling creator-level release through ME29N,
in other words,the manager's release would be cancelled while the creator-level release is cancelled.
So,my question is how to prevent po creator against cancelling self-level release in ME29N.

Cancel release in idoc

Similar Messages

Maybe you are looking for