Issue with IDOC segment creation..

hi,
i created an idoc segment thru we31. when i was saving it, and when the transport request was asked, i cancelled it. it so happend that the underlying structure was created (i was able to see that in se11) but in we31, the segment definition did not appear and i got the message "segment does not exist yet".
so in se11, i deleted the associated structure and tried to recreate the segment, i am not able to !! while saving, i get the error "you do not have authorization for delete for function idoc segment"
when i performed a segment check (ctrl + F1), i got the message,
Repository structure missing for segment ZZZ |
Inconsistent overall length in segment version 000
Segment version 000 not released
Entries exist in table of Segments for segment ZZZ
Entries exist in table of Segment definitions for segment ZZZ
Entries exist in table of Segment structures for segment ZZZ
| Segment ZZZ is inconsistent
what shud i do ?
thks

resolved. seems some authorization was missing. thks

Similar Messages

Issues with ODATA service creation

Hi Gurus,
I am facing some issues with ODATA service creation. I have an analytic view which I want to consume via SAP UI5.
As per guides and blogs, I need to create 3 files, namely .xsaccess, .xsapp and .xsodata. I created these three files but at the same time .xsodata and .xsaccess got created at one more place. That place is my package which I checked out while creating the repository. Now when I try to activate my .xsaccess or .xsapp file, I get an error message - "The file name .xsaccess or .xsapp already exists and only 1 file is allowed per package"
for more info please revert.
Kindly help.
Best regards,
Chandan

Chandan Sinha wrote:
Can we add multiple analytic views in one ODATA service?
Certainly. You just have multiple entities then. You can even create associations between them. Here is an example that uses a combination of CDS Views, Attribute Views, and Analytic Views:
service namespace "Wile.services" {
"Wile.data.models::AN_EPISODES" as "Episodes"
keys ("EPISODE_ID")
navigates ("ToACMEItems" as "ACMEItems",
            "ToCoyoteNames" as "CoyoteNames",
            "ToRoadRunnerNames" as "RoadRunnerNames",
            "ToDirectors" as "Directors",
            "ToWriters" as "Writers");
"Wile.data.models::AT_ACME_ITEMS" as "ACMEItems"
keys ("EPISODE_ID","ITEM_ID");
"Wile.data.models::AT_ACME_CATALOG" as "ACMECatalog"
keys ("ITEM_ID")
create using "Wile.services:ACMECatalogExits.xsjslib::itemsCreate"
update using "Wile.services:ACMECatalogExits.xsjslib::itemsUpdate"
delete using "Wile.services:ACMECatalogExits.xsjslib::itemsDelete";
"Wile.data::WileECoyote.Episode.CoyoteNamesView" as "CoyoteNames"
with ("EPISODE_ID","NAME_ID","NAME")
keys ("EPISODE_ID","NAME_ID");
"Wile.data::WileECoyote.Episode.RoadRunnerNamesView" as "RoadRunnerNames"
with ("EPISODE_ID","NAME_ID","NAME")
keys ("EPISODE_ID","NAME_ID");
"Wile.data::WileECoyote.Episode.DirectorsView" as "Directors"
with ("EPISODE_ID","NAME_ID","NAME","URL")
keys ("EPISODE_ID","NAME_ID");
"Wile.data::WileECoyote.Episode.WritersView" as "Writers"
with ("EPISODE_ID","NAME_ID","NAME","URL")
keys ("EPISODE_ID","NAME_ID");
association "ToACMEItems" principal "Episodes"("EPISODE_ID")
   multiplicity "1"
   dependent "ACMEItems"("EPISODE_ID") multiplicity "*";
association "ToCoyoteNames" principal "Episodes"("EPISODE_ID")
   multiplicity "1"
   dependent "CoyoteNames"("EPISODE_ID") multiplicity "*";
association "ToRoadRunnerNames" principal "Episodes"("EPISODE_ID")
   multiplicity "1"
   dependent "RoadRunnerNames"("EPISODE_ID") multiplicity "*";
association "ToDirectors" principal "Episodes"("EPISODE_ID")
   multiplicity "1"
   dependent "Directors"("EPISODE_ID") multiplicity "*";
association "ToWriters" principal "Episodes"("EPISODE_ID")
   multiplicity "1"
   dependent "Writers"("EPISODE_ID") multiplicity "*";

ECC6.0 upgrade issue with IDoc release

Hi experts,
we are in the process of upgrading our ECC environment from 5.0 to 6.0. We have quite a few interfaces which use ORDERS/Invoice Idocs in customised form. In ECC5.0 environment, we had developed a Z segment in the ORDERS Idoc and the segment release was set as 640. Everything worked fine in ECC5.0.
In upgraded environment, SAP has released new version of some segments. one of those is E1EDP01. This segment has 2 new versions in ECC6.0 environment - 007 and 008. This change in the version changes the data in the IDoc and hence interface goes in error at the EDI provider.
We have tried to use 640 as the IDoc segment release in the partner profile of the IDocs. This still gives us an issue because the 007 version of the segment E1EDP01 has release 620 and hence the Idoc picks up 007 version instead of 006 version as desired. When we change the partner profile with Segment release in the IDoc type as 46C, it gives us an issue in the Z segment saying that the IDoc segment is not released in 46C and the Idoc goes in error.
has any one faces such situation in the past? if yes, please throw some light.
Thanks in advance.

Hello,
Iam new to SAP. Thars why i cant understand well to do upgrade,
Then i found out some notes from internet about Upgrade : SAP Note Number 857904 (upgrade from Release 6. To 7.0).
In that notes,
Actually i would like to know about some key words (for example : ASSIGNING, REPLACE, TRANSFER. ) which how to work in the Release 7.0
Always i have some objets in 4.6C.
Ex 01: READ DATASET p_dataset INTO wa_record
Ex 02 : TRANSFER i_crhu TO p_crhd
LOOP AT i_crhd.
*disable controls in crhd
    PERFORM f_disable_crhd.
    TRANSFER i_crhd TO p_crhd.
    IF sy-subrc NE 0.
      MESSAGE a045.        "Error when transfering data to error file
    ENDIF.
ENDLOOP.
CLEAR i_crhd.
CLOSE DATASET p_crhd.
IF sy-subrc NE 0.
    MESSAGE a039.                      "Error at close dataset
ENDIF.
OPEN DATASET v_crhd FOR OUTPUT IN TEXT MODE.
And then i have some FM (ex : WS_UPLOAD , WS_DOWNLOAD)
So I have changed the code for WS_UPLOAD by GUI_UPLOAD
                              and WS_DOWNLOAD by GUI_DOWNLOAD
now my problem is to know about some key word which how to work in ECC6 (for example ASSIGNING, REPLACE, TRANSFER. )
thanks in advance
Rathy

Posting Data Issue with IDOC Type : COND_A03

Friends,
I'm posting the data from Middleware(Message Broker) to SAP using the IDOC Type : COND_A03 with Message Type : COND_A.
For this IDOC,I'm populating the below Segment's data.
Segement :E1KOMG:
Fields:
KVEWE,KOTABNR,KAPPL ,KSCHL,VAKEY ,KONDA,MATNR .
Segement :E1KONH:
Fields:
KNUMH,DATAB,DATBI
Segement :E1KONP:
Fields:
KSCHL,STFKZ,KSTBM,KSTBW,KRECH ,KBETR,KONWA,KPEIN,KUMZA,KUMNE,MXWRT,GKWRT,ZAEHK_IND ,KBRUE,VALTG,
VALDT,ANZAUF,MIKBAS,MXKBAS,KOMXWRT,KLF_STG,KLF_KAL
Problem: In SAP, IDOC's are processing successfully with status 53 and updating the tables : KONH,KONP successfully.
But Table A957 which is passing against KOTABNR field is not pupulating with the Materials passing.
Can anyone please guide me why the Materials are not populating in the table : A957.
Regards,
Sreeram

Hi,
I guess there might be some issue with VAKEY population.
All the key fields in A957 should be concated properly while populating VAKEY. (Leading zeros must be prefixed to the material)
Regards,
Ganga

Issue with valuation segment and gl in MB5l

Hi gurus
I have an issue with a couple of materials in a report in MM MB5L list of stock values. The materials they are reporting with the issue have no costing screen extended in MM and I think this maybe the issue. The message I am getting is:
Account 121160 does not exist in company code 0010 G/L accnt is missing for val. segment 000005 1400.
I have checked the account and it does exist in the company code, is there any other config between the segment and gl account.
regards

The transaction is MB5L which is stock values balances. The message is:
Account 121160 does not exist in company code 0010
G/L accnt is missing for val. segment 000005 1400,
There is no message number, no question mark(help) to check the message number either, as it is just text at the bottom of the report showing the error.
I thought it might just be because the costing view was not setup, however not sure why the gl account is coming up as cannot see any postings to this account? It maybe that they have not done the relevant MM configuration. The gl account is a material management account.
thanks

Issue with IDOC occurence and SeeBurger message mapping

Hey Guys
While developing a EDI 850 to IDOC scenario i came across this issue with pre-delivered Seeburger mapping(A_850_V4010_to_I_ORDERS05).
I actually need to post multiple IDOC's to SAP system in the same message so i changed the IDOC occurence to unbounded and re-imported that as a .XSD file in Integration repository.
Earlier the pre-delivered message mappings provided by SeeBurger(under SEEBURGER_HIGH-TECH, 1.7.1 of seeburger) was working fine for me since i was posting only 1 IDOC but now the mapping is failing as the IDOC occurence has changed(unbounded).
Is there a way we can do some settings on SeeBurger server or Bic so that we can use the pre-delivered mapping for Multiple IDOC's as well?
I just want to make sure before i start off with doing whole of the mapping manually.
Thanx
Aamir

Thanx for the input guys
@Deepthi.
Doing whole of mapping manualy is definitely the last option but i m looking for ways to re-use the pre-delivered SeeBurger mapping.
>>Seeburger Mapping is only just to convert XML to EDI and EDI to XML.
Bic mapping designer does this,i m dealing with message mapping of XI(convert source to target) not Bic designer right now,and Bic does more than just XML to EDI and vice versa,it handles other industry standards too.
@Jens
>>The XI message mappings from Seeburger in the Industry solutions are mapping templates
Yeah,but the mapping template i have deals with 850 to ORDERS05,when i change IDOC occurence and re-import it back in Integration repository,it doesn't stays as ORDERS05,it has to be changed to user defined message interface(in my case MI_ORDERS05) so i m unable to use 850 to ORDERS05 template.
@Seshagiri
>>Open the Seeburger SWCV From the IR--goto External Def---Select the right one and copy it and paste it in notepad.
Changing the occurence is not an issue,i want to re-use the pre-delivered mapping in Integration repository,which is not working.
Looks like i need to do it manually
Thanx
Aamir

Could not trace the issue with IDOC to file

Hi All,
We are facing issue with missing idoc data in the file, There were 20 idocs got generated (msg type - PAYEXT) from the payment run but only 15 of them written to the file, in the Outbound partner profiles we are using file port to create file. Noticed that all idocs were showing the same status (03) and The IDoc was written to file & file location.
When we checked the file and found that 5 idocs data was not written to the file, but surpricingly status was showing that it was written to file. Can any one give clue / similar experience ... on this. Not sure how to track the issue ... i checked SMQ1, but nothing was locked.
Thanks
Satya

Hi Kumar,
As Jose mentioned please check the occurrence of the 6th file. It should be 0..unbounded. Also if you do this it will pass the mapping but you will get the error for the 6th file in sxmb_moni, because it would be an empty root message only. This is a known issue and I dont think we have a solution for this. But one workaround would be to create a custom mapping exception so that you have that exception in sxmb_moni when the message fails and if you have alerts then you will have this mapping exception in your alert.
Regards,
---Satish

Outbound Idoc Segment Creation via BD52 trigger

hi all,
i am new to Idocs so please forgive me if i am missing the obvious. i am using standard the material master Idoc type MATMAS05 to transmit any material master changes to an existing legacy system. i set up some fields in BD52 to trigger an Idoc when they are changed. the problem is when i change a field in the MARC segment (ie: MARC-PRCTR - Profic Center) 3 segments are generated (E1MARAM, E1MAKTM, EIMARCM), but when i change something in the MARA segment (ie: MARA-PRDHA - Product Hierarchy) only E1MARAM and E1MAKTM are sent.
the receiver is set up for all three Idoc segments so when only 2 are sent it errors out. how can i force all 3 segments to send every time?
many thanks.
James Hinkin

Hi, I think you must be running the program RBDMIDOC to send an IDoc based on the change pointers.
SAP has designed such a way that it will create IDocs only with changed data. In other words, E1MARAM is always populated as it is header data. Its obvious that you dont want to send the data that is not changed. Hence if you are changing Product hierarchy, only relevent segments are populated with values.
If you still want to send all the data irrespective of whether those fields are changed or not, either you may have to code in a user-exit to populate these fields(segments) or, change the program accordingly.
Hope this helps you and let me know if you need further help
Vamsi

Changing filed name description - idoc segment creation/change

HI,
is it possible to change the fieldname description in an IDoc Segment without changing the DataElement ?
Exampel:
I Used CHAR40 as dataelement for my own ZZFIELD. In the Idoc the fieldname description of the data element CHAR40 is shown.
Can i change this description ?
thx,
Gordon

No, The IDOC always displays the texts based on the Data Element which is assigned to that field. If you want to display your own text you have two options:
1. Create an enhancement and change the text of the data element which is not recopmmended because it will be changed wherever that data element is used.
2. Instead just create an own data element where you can maintain any texts you need.
Hope that helps,
Michael

Issues with IDOC strucuture in XI

Hi all,
I tried to import IDOC structure(ZDESADV.DELVRY01.Z1DELVRY) from SAP box in Integration Repository . After importing , That Idoc strucuture is getting linked with ZDESADV.DELVRY02.Z1DELVRY .
Like the view from IR is
Display IDoc
Name             : ZDESADV.DELVRY01.Z1DELVRY
Namespace    : urn:sap-com:document:sap:idoc:messages
Software Component Version :
Description:
(Tabs)Struture/XSD/WSDL ( In structure Tab)
Structure          Categary                     type
Z1DELVRY     Element
IDOC            Element                     ZDESADV.DELVRY02.Z1DELVRY
BEGIN          Attribute                     xsd:String
EDI_DC40      Element                      EDI_DC40.ZDESADV.DELVRY02.Z1DELVRY
Then is it not generating the fields of EDI_DC40 segment .....
My question here is , Why this Idoc type is linked with DELVRY02 but I only Imported DELVRY01. It is really creating issue.
Does anyone have any idea where the issue.
Whether it is in XI box or SAP box ?
Thanks
Laks

Hi lakshmi s ,
Please elaborate the solution... where was this idoc not properly linked??
I am facing the same issue and need the solution very urgently!!
Thanks n regards
VJ
Edited by: newbpi on Mar 9, 2010 4:56 AM

Issue with Auto PO creation

Hello Gurus,
Kindly help me with this issue.
I have user who is using ME59 for the auto PO creation.When he runs this transaction with the "TEST RUN" flaged,in the result screen he is able to see a mesasage as "PO creation successfull" along with the vendor number for which PO has been created.
But along with above message he also needs material number & quantity for which the PO has been created.
Kindly let me know how to proceed with this request.

It is not possible in standard , not for test run and not for production run, not with any customizing and I have not found any OSS note that may allow that.
For any further information in the log you have to modify the program.

Issue in Idoc Segment.

Hi Gurus,
i have a problem in Idoc, while creating output type for a Billing document that time one segment repeating lots of time with same data..how to avoid this?
Mohana

Mohana
Are you sure about the segment name E1EDK01 ?? Becoz.. Only one Segment of type E1EDK01 is allowed in one IDOC...
See below for details:
Segm.type       E1EDK01
Minimum number 1
Maximum number 1
Parent segment
Hier.level      1
Thanks
Amol Lohade

Problem update IBAN bank details with IDOCs segment E1KNBKM

Hi all,
i use Idoc DEBMAS07 in which i use the segment E1KNBKM to create IBAN in customer bank details. If bank details do not exist, the IDOC is integrated, IBAN is created.
If i recreated the same Idoc, with same data (just change bank name) the Idoc is in error with the message : 'No batch input data for screen SAPMF02D 0130'.
In debugging, we see that the dynpro sequence is wrong. For vendors it's work. I can create and update IBAN.
i don't find SAP notes, or help forum on this problem.
Any ideas ?
Thanks
Edited by: ToraTora on Aug 17, 2011 11:16 AM

maybe you are the first who encountered this error, open a call at SAP yourself

ZHRMD_A Custome message type issue with custom segments.

Hi Experts,
We have implemented ALE in HR system, we have all other ALE using HRMD_A and we have jobs scheduled for HRMD_A message type. We dont want this job should trigger our model and distribute the data. So we have reduced the HRMD_A messae type to ZHRMD_A for basic type HRMD_A06. Every thing fine. After upgrade of SAP FROM ECC6.O to EHP4, PFAL is not creating IDOC segements for custom segments Z*. for example Z1P0002....ETC, though there is personal data for PERNR.
Please guid if you have come across such situation and solution.
Thanks & Regards.
Venkat.

Hi Venkat,
In the same way i too have one situation like...have different model view with same message types( and same extension type) for various countries from one sender system.
Should i create reduced message type for each model view?
Or can i use same message type HRMD_A for various model views?
If i can use same message type and same extension type for various model views is there any restriction we need to write in USER EXIT EXIT_SAPLRHA0_004?
Regards,
Lava.

Acknowledment issue with idoc Adapter

Hello all,
I've an interface process that send a specific idoc from SAP R/3 4.7 to SAP XI 3.0.
This Idoc is known at XI side in IDX2 transaction.
Each time XI receives this kind of idoc, it processes an acknowledgment (sends back an ALEAUD idoc to my SAP R/3)
with followings data in E1ADHDR / E1STATE segment :
DOCNUM     0000000002401038
STATUS     51
STAMQU     SAP
STAMID     IDOC_ADPAPTER
STAMNO     000
I don't want this ack idoc to be sent but I don't manage to find where customize Idoc adapter to send it.
Can you help me ?

HI,
Make an entry in the table IDXNOALE in XI system by providing the details for the port, IDOC etc for which the Acknowledgements need to be turned off. You ca check this port etc from IDX1 entry in XI server
Or
Go to IDXNOALE report in XI There, click on request acknowledgement button, and in exceptions section, provide the message type for which you donot want acknowledgements.
Regards,
Moorthy

Issue with IDOC segment creation..

Similar Messages

Maybe you are looking for