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

Similar Messages

Error in idoc of basic type artmas05 - status 51 with Message no. MG537

Hi all,
I tried to upload the material master table through idoc creation of basic type artmas05. But when i'm trying to do that i'm getting status 51 with Message no. MG537. then I analysed the application log which displays the following
*The field MARA-MEINS/BAPIE1MARART-BASE_UOM(_ISO) is defined as a required
field; it does not contain an entry
*The field MARA-TAKLV/BAPIE1MARART-TAX_CLASS is defined as a required field; it does not contain an entry
*The field MARA-TRAGR/BAPIE1MARART-TRANS_GRP is defined as a required field; it does not contain an entry
*You have not fully maintained the tax classifications
*The field MAW1-WLADG/BAPIE1MAW1RT-LOADINGGRP is defined as a required field; it does not contain an entry
But i hv given values for all the above fields in their respective segments.So can any1 suggest me how to proceed further.
It would be helpful if someone could tel me the required fields in idoc to upload material master table through idoc.
Thanks in advance,
Revathi.

Hi,
Anybody please tell me the reason for the following error, despite giving all the field values mentioned there. The same error occurs even if I run the BAPI (which the ARTMAS iDoc uses) directly by passing values.
The field MARA-MEINS/BAPIE1MARART-BASE_UOM(_ISO) is defined as a required field; it does not contain an entry
The field MARA-TAKLV/BAPIE1MARART-TAX_CLASS is defined as a required field; it does not contain an entry
The field MARA-TRAGR/BAPIE1MARART-TRANS_GRP is defined as a required field; it does not contain an entry
The field MAW1-WLADG/BAPIE1MAW1RT-LOADINGGRP is defined as a required field; it does not contain an entry
Regards,
Gowri.S

Error :- No authorization for basic types (activity 01)

Hi Experts,
While trying something at the BW server i suddenly got the below error
I am getting the error when i am accessing the T-CODE RSA1.
Error :- You have no authorization for basic types (activity 01)
I checked the ids of my colleagues all are getting the same messages...
Regards,
RG

Hi,
1. Check in SU53 tcode
2. You are having RSECADMIN/PFCG tcode access?? If yes you can give authorisation for the same.
3. You dont have S_RS_ADMWB - authorisation
4. for your user id give this above authorisation
5. If you are unable to do the same, ask your basis team to give you the authorisation
refer this link- 1.http://help.sap.com/saphelp_nw70ehp1/helpdata/en/f3/291542e4b4df2ce10000000a1550b0/frameset.htm
2.http://help.sap.com/saphelp_nw70ehp1/helpdata/en/a4/1be541f321c717e10000000a155106/frameset.htm
Edited by: Asish Sahu on Apr 28, 2009 10:34 AM

Error :- No authorization for basic types

Hi Experts,
While trying something at the BW server i suddenly got the below error
I am getting the error when i am accessing the T-CODE RSA1.
Error :- You have no authorization for basic types (activity 01)
I checked the ids of my colleagues all are getting the same messages...
Regards,
RG

Hi,
analyze the missing authorization with transaction SU53 immediately when the error appeared.
Ask your system/authorization administrator to grant you the missing authorization.
Regards
Rainer

Basic type CREMAS03 does not exist

Hi all.
We have SRM 7 Classic Scenario with ECC 6.4
My problem is in scenario MM-SUS. When we try to replicate a vendor data from MM to SUS the idoc MM is processed correctly, but in (SUS) has an error in trx WE05: Basic type CREMAS03 does not exist.
I review the settings and I can not find the cause.
any idea about that?
Regards

Hi,
I am not clear with your issue. Why are you checking for idoc status in SUS system?
IDOC is sent from the ERP system and check what the status of IDOC is in ERP. Next check whats the xml status in PI system and if its successful in PI then check xml in SUS system/. You can check xml status using tcode: sxi_monitor.
Regards
Sam

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

Error while releasing Billing: Assign HD00 (Frieght) Condition type in COPA

Hi,
I am getting the below error while releasing billing document.
Assign condition HD00 type in COPA
HD00 condition type is frieght condition type
Is it good thing if we assign this condition type to COPA value field in KE4I? or we should not assign Frieght condition to COPA?
Please advise
Thanks
Kishore

HI Kishore,
To which GL account are you posting this freight condition value? Is that GL created as a revenue element (of category '11'/'12')?
If yes (has to be 'yes', since you are getting the error message), then you don't have a choice but assigning a CO-PA value field in KE4I. The idea here is, if you have created the GL as revenue element, then you intend to take it to Controlling module for further analysis. Thus, making your FI/CO reconciliation easy.
If you do want to carry this value to CO-PA for analytical reporting then don't create that particular GL (assuming you are posting freight to a separate GL) as a revenue element. That said, it does make sense to carry this value to CO-PA and in your present case, you don't have a choice as the message which you got is an error message, which you can't circumvent.
Hope this helps.

IDOC communication between different basic type releases.

Has anyone run into a scenario where a newer SAP release would like to send a message to a partner with an older SAP release, using a basic type that does not exist in the older system? (eg. DELVRY05 which only exists in release 700)
In this scenario, what is the best practice, other than to have the newer SAP system send an older basic type that does exist in the receiving partner?
Thanks.

Hi,
You can do this by specifying the older release in the partner profile outbound settings (for message type).
Under the "Outbound options" tab there is a field "Seg. release in IDoc type". There you can specify the older release and the IDoc will automatically be depricated when it is received in the receiving system.
Regards,
Gajendra.

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

IDoc basic type FIDCCH01 with error F5866

Iu2019m trying to create an iDoc with basic type FIDCCH01 and message type FIDCCH type. Iu2019m getting error F5866 u201CWhen calling up the interface to financial accounting, no entry was made in the transfer parameter "Application key" when I process the idoc. I do not see an idoc value by this name. What am I missing in my config?
Thanks,
Stan

Stan,
First, I'd like to mention that you determine where the error message F5866 is used by entering this message in transaction SE91 and pressing the where-used function. This won't show you any of the dynamic message calls, but it does indicate that function modules FI_DOCUMENT_CHANGE and FI_DOCUMENT_CHECK_CHANGE are both possible origins for the message you received. These function modules are part of the FI Interface which I am assuming is called during the processing of your IDoc.
ACCHD-AWREF is one of the values passed to the FI Interface function modules, and message F5866 is returned when that field is blank. This is why I assume that the IDoc in question is missing a value for the AWREF field.
Based on that assumption, I checked the definition for the IDoc type that you mentioned, FIDCCH01, via area menu WEDI. This IDoc type contains a segment E1FIREF with field AWREF. You can use transaction WE02 to display the IDoc causing the error and check to see if the actual data for E1FIREF-AWREF is blank (ultimately leading to the blank ACCHD-AWREF value and error F5866).
Cheers,
Jamie

Release? while assigning Z Message Type to a Standard SAP IDOC Basic type

Hi Experts,
Am trying to assign a custom Message Type to a Standard SAP IDOC Basic type in WE82 transaction, but am not sure How to find the Release(last column of WE82 Tx)? Pls. let me know.
Thank you

Hello,
In case of IDOC, Go to Transaction WE30, type your IDOC name & select basic type & extension.
After that select Go to -> Header data (Shift+F7), you will Idoc header info. In the same pop-up you will find IDOC release for which version.
Regards,
Sameer

How to rectify the error "basic type z_idocname could not be converted"

hi,
I am trying to create a partner profile for a outbound process. In the transaction we20 i gave a new partner number, attached the message type and the idoc and the port no, when i tried saving its showing basic type z_idocname could not be converted how to rectify this error.

Have you made the corresponding entries in WE81 and WE82?

Error: Basic type 'WVINVE03' is unknown

hi sdn frnds
I am doing File to Idoc scenario in that i am getting the error as
Error: Basic type 'WVINVE03' is unknown
can any one know about this and how to solve this problem
thanks in advance
Vasu

Hi,
where do you try to find this idoc?
this IDOC should only be in the R3
(not in the XI)
if you want it in the XI you need
to download it's sigmature in <b>integration repository</b>
just like described here:
http://help.sap.com/saphelp_nw04/helpdata/en/2b/a48f3c685bc358e10000000a11405a/content.htm
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

Data Services IDOC Errors when working with a newl Basic Type

Hello,
Just wondering if anyone else has encountered an issue similar to the one I am dealing with. We are trying to create business partners in SAP CRM from Data Services via IDOC. We are not using the standard IDOC, but instead we are using a new IDOC type.
This IDOC type is generated by SAP CRM automatically through a transaction BDFG. This transaction creates a new basic type for an standard IDOC with the additional fields that we have added through the easy enhancement workbench (EEWB).
The issue that we are having is that when we import the IDOC type into data services and we look at the schema many fields and sub-structures of the IDOC are duplicated. This means that we receive hundreds of errors when we try to validate our data flow. I can delete the duplicated sub structures in my query transformation but then the query transformation and the output schema and the idoc input schema are no longer identical.
I have searched all over oss and different web forums for a solution but no one else it seems has even encountered this error. If anyone else has had a similar issue and can offer help it would be greatly appreciated.
Bill

Issue is resolved.
After importing the meta data for the IDOC into data services I then proceeded to edit out all of the duplicate structures and fields from the IDOC.
After making the IDOC structure in data services identical to the structure of the IDOC in SAP I then proceeded to test this IDOC and it executed successfully.

Error While Releasing Accounting Document & Proforma Invoice--URGENT

Dear Gurus,
I am facing problem in below cases.
-- Proforma Invoice canot be cancelled ....If i need to cancel then wht needs to do
-- I created New Material Master again old material and made sale getting Acc determinatin error while releasing accouting document.. But in old cases( old material) no problem like this. Y like this.
Pls guide me.
Regards,
Venkat

Dear All,
Thanx your kind replies. I analysis and foud following:
Access       Message                    Description
05       123                    Access ZKOF not carried out
Access     Complete
Field Condition Table          Value in Doc
Chart of Accts          CAIN
Sale Org                          1000
Plant                           F201
AccAssg Grp          01
Acct Assgn. Grp          05
Account Key          !! ( Showing Yellow Indicator)
Above things showing Against Condition TYpe JEXT.
I checked in Pricing procedure and condition Type JEXT....against this no Accounting key assigned.
No problem faced earlier...now showing like this........y.
Regards,
Venkat

Error Cancelling Release of Basic Type

Similar Messages

Maybe you are looking for