SPEC2000

Hello,
I am trying to configure the Interface for SPEC2000 in our system but we are facing some problems. We did the configuration for Order Acknowledgement and Order Change. I am using the FLATFILE_TO_SPEC2K to simulate a Inbound processing but the system sends the error message ME 709. It seems to search for a Purchase Document (MM). How can I fix it? Does anybody has some material about this configuration? How to configure the Conversion Rules?
Thanks in advice.
Lourdes

Hi Maria,
The function used by you is correct. You have to set up Conversion Rules (BD55) and WE20 Inbound Partner profile(if u are looking @ inbound sales orders, use Msg.Function : MM).
Joe G A

Similar Messages

Spec2000 / Spec2k trigger S1PNSTAT via ME23

Hi Experts,
Does anyone knows how to trigger S1PNSTAT via ME23.
I tried using
   1.      From the SAP Easy Access menu, choose Logistics-> Purchasing ->Purchase Order -> Display Extended Purchase Order.
       2.      Enter the purchase order and choose Continue.
       3.      Select an item and choose Item ->More functions -> Additional data.
The additional data screen for the order item appears.
       4.      Choose Item ->SPEC2000 ->Send S1PNSTAT.
The message no data change appears. No matter how I change the PO, it doesn't get trigger.
Anyone have any idea?
Regards,
Clarice
http://help.sap.com/erp2005_ehp_04/helpdata/EN/88/7e8a1b422c45f1b8e57b45382dda9c/frameset.htm

Oh I realised it in item level ---> additional function ---> more function ---> spec2000 ---> send S1PNSTAT

ME21N / ME22N / ME23N Spec2000 tab is missing

Dear All,
Once we implied the lastest support package into our system, the Spec2000 tab which was shown at the bottom of the ME21N - ME22N - ME23N pages dissapeared. I have investigated this issue for two weeks but the result is "FAIL". Quick help is needed.
Best Regards.
Eray

Thanks for the quick response, but I have already implemented this OSS Note into our system. However, problem remains as it is.
Let me explain another way. The problem is mainly about the customization problem, I think. In my opinion, I have to activate Spec2000 tab through SPRO, but I don't know the relevant activation process. Furthermore, if any enhancement package is infected because of the Support Package, this case needs to be taken into account.
Thanks in advance.
Eray

BizTalk 2010, Circular type reference with Spec2000 Xsd

Hello,
For a electronic invoices solution, we are using the Spec2000 standard.
My invoice schema "ATA_SparesInvoice.xsd"
Includes "MM_CommonTypes.xsd"
Which includes "CSDD_MM.xsd"
Which includes "ATA_CommonTypes.xsd"
I am receiving ATA_SparesInvoice from our supplier without any problem through an HTTP receive-send port using XML pipeline.
But I'm now trying to send a ATA_SparesInvoice message through an HTTP POST send port, and I get the following error:
"There was a failure executing the send pipeline: "Microsoft.BizTalk.DefaultPipelines.XMLTransmit, Microsoft.BizTalk.DefaultPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "XML assembler" Send
Port: "EDI_ResubmitInvoice_HTTP" URI: "http://server.domain/CHC.EDI.Submit/BTSHTTPReceive.dll?Invoice" Reason: Circular type reference."
There are a lot of types in the schema, do you know any tools that could validate the schema and pinpoint the circular reference?
Do you know why am I receiving the error only in the XMLTransmit pipeline and not in the XMLReceive?
One option I have is to remove the "include" and to replace the element ref by the actual base types. But all changes will be lost when schema will be updated to a newer version.
Any other suggestions on how to solve this?
Thank you :)

Hi,
Can you try to use the PassThru pipeline on this send port instead of XMLTransmit and share the results. It should not give you this error if
you use PassThru pipeline.
You only need to use XML Transmit when you want to promote any of the to-be-send messages to the context. If you don’t need
to promote any value while sending, then you can use PassThru transmit.
Your issue due to the circular import problem where one schema imports another
XSD schema, and vice versa.
Rachit
Please mark as answer or vote as helpful if my reply does

Spec2000/SC tab

Hello,
I need to gray out all fields in SPEC2000/SC tab in the Purchase order. Is it possible to gray out following fields.
-Mod.ID.CD
-Order priority
-Aircraftreg no
Didn't find any field in the PO screen layout configuration.
Thanks for your kind advise....

Hi,
Please check the note: 824502 - Field selection for Spec2000 fields in enjoy PO transactions
An alternate solution will be creating a transaction variant for ME21N in SHD0 transaction.
Regards,
AKPT

Activating SPEC2000 tab in ME21N...

Hi all,
I'm working on ECC 6.0 and I need to activate SPEC2000 tab in Purchase Order.
This all works in DI and A&D industries.
Does anyone know how can I activate it?
SAP Note 512922 describes my problem.
Thank you for your quick answer!

Hi
For Consignment Process the Inforecord maintained will serve you the Purpose of the Condition Tab, So you need to maintain all the Conditions in the Purcjase inforecord
I dont think it is possible to get the Conditions Tab with Item category K
Thanks & Regards
Kishore

How to populate the field Discount Percent (DIS) in the outbound S1ORDEXC?

Hello all,
I am working with the Spec2000 to send out the IDOC S1ORDEXC.
Does anyone know how to populate the field Discount Percent (DIS)?
This field length of Discount Percent is 2 characters, but our customer discount in the Princing Conditions (Sales Order) is longer than 2 characters (ex: 7.500-%)
Thank you

Hello Thuan
I guess you are working with IS- ADEC and SPEC 2000. I am not an expert on this but leave you some hints from OSS notes I came across.
It appears like Discount Percent - DIS and Procurement Discount Percent -PDP are complementary and mutually exclusive. If one exists, the other need not.
Looks like DIS is computed as (100-PDP)/100 and it is just a 2- integer data (as in 20 Percent). It is a kind of multiplier (Factor), example if PDP discount is 10 percent, then DIS (Factor) is 0.9 and so final (net) price after discount = Price*0.9.
" If the discount comes in the S1BOOKED inbound into SD in the field DIS, then the discount has to be sent back in the DIS field .. if it came in the PDP field then it has to be sent back in the PDP field. If there was no discount in the incoming IDoc, then the discount has to be filled in the PDP if there was a change in the discount".
KDATE in SPEC 2000 file maps to DIS and KPERC to PDP.
PDP has 4 characters and per OSS note 440380, the point is ignored meaning you can work with 1225 instead of 12.25.
So may be you can work with PDP?
OSS notes: Apply to older releases but may still be applicable conceptually speaking.
456153 - S1ORDEXC does not send out Discount
440380 - PDP has only 4 characters in the SPEC IDoc instead of 5
596042 - Discount percent DIS not considered e processing S1ORDEXC
698668 - Incorrect calculation of unit price for PO item by S1ORDEXC
Let me know you final findings.

EDI to RFC interface

Hi,
I'm about to implement Spec2000 to RFC interface. since XI does not support EDI (no EDI adaptors available) i'll have choose one out of two options:
1. manipulate EDI as it was regular text file.
2. use 3rd party tool as an adaptor.
i belies my first option is complicated and clearly has great risk, so i'm looking for as much leads as i can get.
Tnx in advance
Uri

>
uri karagila wrote:
> Hi,
>
> I'm about to implement Spec2000 to RFC interface. since XI does not support EDI (no EDI adaptors available) i'll have choose one out of two options:
>
> 1. manipulate EDI as it was regular text file.
> 2. use 3rd party tool as an adaptor.
>
> i belies my first option is complicated and clearly has great risk, so i'm looking for as much leads as i can get.
>
> Tnx in advance
>
> Uri
Option 1 - I guess that is not a good idea considering the complexity in EDI messages. But then it denpends how many interfaces you have. If there are very less say under 10 interfaces using the EDI spec. then it is still worth investing time and money on coming up with the manipulation but else.... its a night mare.
Option 2 - There are various third party adapter available ex. seeburger, iway etc which you can make use. Only thing is it comes with a cost but life becomes much easier.

Need Help on complex XML loading into ODI

Hi,
I have a requirement in which i have to create xml mapping in ODI which should load 30 to 40 million message per day with file size of 30 MB. I have created xml connection in topology manager and have provided xsd path of unix server and it's working but when I try to reverse xml structure into Designer model then it gave me error " java.sql.SQLException: No DTD found and no XML file provided: the XML schema cannot be created". I have used below xml connection detail in topology manager.
JDBC Driver: com.sunopsis.jdbc.driver.xml.SnpsXmlDriver
jdbc:snps:xml?f=/odi_rep/sita_meg_bi/etl_metadata/&stypex.xsd&re=TYPEX&ro=true&case_sens=true
We are using 10.1.3.6 ODI version in this project.I have given below xsd and xml file format. FYI...we recevie multiple message with same strucutre in xml source file.
XSD File:
XML File :
<tns1:MessageTraceEvent xmlns_tns1="http://www.sita.aero/csbu/tools/v1/namespace" timeStamp="2011-07-13T00:01:09Z" priority="3" envelopeMessageID="xs-atl-xs2011-07-13t00:01:09.525:519160" mes
sageType="TYPEX" messageTotalSize="6506" systemID="bgtxjao">
 <tns1:SitaIdentifiers>
 <tns1:sitaUID>xPreg1D3RF2tGbF9iUPReA</tns1:sitaUID>
 <tns1:TransactionID>dzA5Arb0QZyOOq9NqgrQ2Q</tns1:TransactionID>
 </tns1:SitaIdentifiers>
 <tns1:previousSitaIdentifiers>
 <tns1:sitaUID>xPreg1D3RF2tGbF9iUPReA</tns1:sitaUID>
 <tns1:TransactionID>zrL7EtGpTVSYeLpb+2W1NQ</tns1:TransactionID>
 </tns1:previousSitaIdentifiers>
 <tns1:Addresses>
 <tns1:Originator>XS-ATL-XS</tns1:Originator>
 <tns1:Recipient>AF-QVI-BP</tns1:Recipient>
 <tns1:Recipient>AF-QVI-BP</tns1:Recipient>
 </tns1:Addresses>
 <tns1:RemoteSystem>
 <tns1:Source>
 <tns1:NodeID>AF-QVI-BP</tns1:NodeID>
 <tns1:MiscData>BadgerID: XS-ATL-XS-1310515269-9.1</tns1:MiscData>
 <tns1:isCustomer>false</tns1:isCustomer>
 </tns1:Source>
 </tns1:RemoteSystem>
 <tns1:AdditionalData>
 <tns1:TypeXData subject="No message"/>
 </tns1:AdditionalData>
 <tns1:Payload payloadType="MessageData">PHR4bWU6VFhNX0VudmVsb3BlIHhtbG5zOnR4bWU9Imh0dHA6Ly93d3cuaWF0YS5vcmcvdHhtL2VudmVsb3BlIiB4bWxuczp0eG1zPSJodHRwOi8vd3d3LmlhdGEub3JnL3R4bS9zZXNzaW9
uIiB4bWxuczp0eG1tPSJodHRwOi8vd3d3LmlhdGEub3JnL3R4bS9tc2doZWFkZXIiIHhtbG5zOnR4bWM9Imh0dHA6Ly93d3cuaWF0YS5vcmcvdHhtL2NvbW1hbmQiIHhtbG5zOnR4bXg9Imh0dHA6Ly93d3cuaWF0YS5vcmcvdHhtL3hhdGFwIiB4bWxucz
p0eG1mPSJodHRwOi8vd3d3LmlhdGEub3JnL3R4bS9mYXVsdCIgeG1sbnM6dHhtcj0iaHR0cDovL3d3dy5pYXRhLm9yZy90eG0vcmVwb3J0IiB4bWxuczp0eG11PSJodHRwOi8vd3d3LmlhdGEub3JnL3R4bS9hdXRoIiB4bWxuczp0eG1hPSJodHRwOi8vd
3d3LmlhdGEub3JnL3R4bS9hdHRh
pc3Rvcnk+PC93dHI6QklSX0RlbGF5ZWRCYWdSZWNvcmQ+CgkJPC90eG1lOlRYTV9QYXlsb2FkPgoJPC90eG1lOlRYTV9Cb2R5Pgo8L3R4bWU6VFhNX0VudmVsb3BlPgo=</tns1:Payload>
</tns1:MessageTraceEvent>
Edited by: user13544580 on Jul 18, 2011 6:27 AM

<?xml version="1.0" encoding="UTF-8"?>

XSD File :
<xs:schema xmlns:tns1="http://www.sita.aero/csbu/tools/v1/namespace" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:ns1="http://www.sita.aero/csbu/tools/v1" targetNamespace="http://www.sita.aero/csbu/tools/v1/namespace" elementFormDefault="qualified" attributeFormDefault="unqualified" version="version 1.0">
 <xs:element name="MessageTraceEvent">
 <xs:annotation>
 <xs:documentation>version 1.0</xs:documentation>
 </xs:annotation>
 <xs:complexType>
 <xs:sequence>
 <xs:element name="SitaIdentifiers" type="tns1:SitaIdType">
 <xs:annotation>
 <xs:documentation>Container for Sita Unique ID and Transaction ID</xs:documentation>
 </xs:annotation>
 </xs:element>
 <xs:element name="previousSitaIdentifiers" type="tns1:SitaIdType" minOccurs="0" maxOccurs="unbounded">
 <xs:annotation>
 <xs:documentation>Container for previous Sita Unique IDs and Transaction IDs</xs:documentation>
 </xs:annotation>
 </xs:element>
 <xs:element name="relatedSitaIdentifiers" type="tns1:SitaIdType" minOccurs="0" maxOccurs="unbounded">
 <xs:annotation>
 <xs:documentation>Container for related Sita Unique IDs and Transaction IDs which a delivery report is reporting</xs:documentation>
 </xs:annotation>
 </xs:element>
 <xs:element name="Addresses">
 <xs:annotation>
 <xs:documentation>Container for Sender and Recipient addresses</xs:documentation>
 </xs:annotation>
 <xs:complexType>
 <xs:sequence>
 <xs:element name="Originator" type="tns1:AddressType" minOccurs="0"/>
 <xs:element name="Recipient" type="tns1:AddressType" minOccurs="0" maxOccurs="unbounded"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 <xs:element name="RemoteSystem">
 <xs:annotation>
 <xs:documentation>Container for Source or Destination system information</xs:documentation>
 </xs:annotation>
 <xs:complexType>
 <xs:choice>
 <xs:element name="Source" type="tns1:HostType"/>
 <xs:element name="Destination" type="tns1:HostType"/>
 </xs:choice>
 </xs:complexType>
 </xs:element>
 <xs:element name="AdditionalData" minOccurs="0">
 <xs:annotation>
 <xs:documentation>Service or Billing specific information</xs:documentation>
 </xs:annotation>
 <xs:complexType>
 <xs:choice>
 <xs:element name="AFTNData" type="tns1:AFTNDataType" minOccurs="0">
 <xs:annotation>
 <xs:documentation>Addintinal data gathered on NTS </xs:documentation>
 </xs:annotation>
 </xs:element>
 <xs:element name="TypeBData" type="tns1:TypeBDataType" minOccurs="0">
 <xs:annotation>
 <xs:documentation>Additional data gathered on MegaSwitch, Sitex or Badgers</xs:documentation>
 </xs:annotation>
 </xs:element>
 <xs:element name="TypeXData" type="tns1:TypeXDataType" minOccurs="0">
 <xs:annotation>
 <xs:documentation>Additional data gathered on Badgers</xs:documentation>
 </xs:annotation>
 </xs:element>
 <xs:element name="SMTPData" type="tns1:SMTPDataType" minOccurs="0">
 <xs:annotation>
 <xs:documentation>Additional data gathered on SMTP systems</xs:documentation>
 </xs:annotation>
 </xs:element>
 <xs:element name="FAXData" type="tns1:FAXDataType" minOccurs="0">
 <xs:annotation>
 <xs:documentation>Additional data gathered on Fax systems</xs:documentation>
 </xs:annotation>
 </xs:element>
 <xs:element name="OmhData" type="tns1:OmhDataType" minOccurs="0">
 <xs:annotation>
 <xs:documentation>Additional data gathered on OmhData systems</xs:documentation>
 </xs:annotation>
 </xs:element>
 </xs:choice>
 </xs:complexType>
 </xs:element>
 <xs:element name="Payload" minOccurs="0" maxOccurs="unbounded">
 <xs:annotation>
 <xs:documentation>Used to save the full message as received from customer, it can help us avoid re-transforming it back to original message or be used for debugging</xs:documentation>
 </xs:annotation>
 <xs:complexType>
 <xs:simpleContent>
 <xs:extension base="xs:base64Binary">
 <xs:attribute name="payloadType">
 <xs:simpleType>
 <xs:restriction base="xs:string">
 <xs:enumeration value="MessageData"/>
 <xs:enumeration value="EnvelopeData"/>
 </xs:restriction>
 </xs:simpleType>
 </xs:attribute>
 </xs:extension>
 </xs:simpleContent>
 </xs:complexType>
 </xs:element>
 </xs:sequence>
 <xs:attribute name="timeStamp" type="xs:dateTime" use="required"/>
 <xs:attribute name="priority" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation>Priority defines precedence in sending the messages through to destination</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="bodyMessageID" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation>The Message ID in the body, as received from or sent to the customer.</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="envelopeMessageID" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation>The Message ID in the envelope, as received from or sent to the customer.</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="isReport" type="xs:boolean" use="optional" default="false">
 <xs:annotation>
 <xs:documentation>Is it a delivery or acknowledge report? If so, set it true</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="messageType" type="tns1:MessageType" use="required">
 <xs:annotation>
 <xs:documentation>The type of message, e.g. TYPEB, TYPEX, SMS, etc.</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="previousMessageType" type="tns1:MessageType" use="optional">
 <xs:annotation>
 <xs:documentation>The logical message type, where this is different from the physical type. For example a TYPEB message sent to SMTP would have a messageType of SMTP, but previousMessageType of TYPEB.</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="messageBodySize" type="xs:string" use="optional"/>
 <xs:attribute name="messageHeadSize" type="xs:string" use="optional"/>
 <xs:attribute name="messageTotalSize" type="xs:string" use="optional"/>
 <xs:attribute name="PDM" type="xs:boolean" use="optional">
 <xs:annotation>
 <xs:documentation>True if it is a PDM message.</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="messsageArchive" type="xs:boolean" use="optional">
 <xs:annotation>
 <xs:documentation>True if the message has been flagged for archiving.</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="messageArchiveDays" type="xs:int" use="optional">
 <xs:annotation>
 <xs:documentation>The number of days to archive, if known.</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="systemID" type="xs:string" use="required">
 <xs:annotation>
 <xs:documentation>The unique identifier for the system executing the transaction, e.g. BADGERX, JAOMSW, etc.</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 </xs:complexType>
 </xs:element>
 <xs:simpleType name="MessageType">
 <xs:restriction base="xs:string">
 <xs:enumeration value="AFTN"/>
 <xs:enumeration value="FAX"/>
 <xs:enumeration value="SMTP"/>
 <xs:enumeration value="TYPEC"/>
 <xs:enumeration value="TYPEB"/>
 <xs:enumeration value="TYPEX"/>
 <xs:enumeration value="SMS"/>
 <xs:enumeration value="X400"/>
 <xs:enumeration value="SKYFAX"/>
 <xs:enumeration value="OTHER"/>
 <xs:enumeration value="TELEX"/>
 <xs:enumeration value="URI"/>
 <xs:enumeration value="EDI"/>
 <xs:enumeration value="EDI-X12"/>
 <xs:enumeration value="EDI-EDIFACT"/>
 <xs:enumeration value="EDI-BINARY"/>
 <xs:enumeration value="EDI-XML"/>
 <xs:enumeration value="SPEC2000"/>
 </xs:restriction>
 </xs:simpleType>
 <xs:simpleType name="EventType">
 <xs:restriction base="xs:string">
 <xs:enumeration value="MessageAccepted"/>
 <xs:enumeration value="MessageDispatched"/>
 <xs:enumeration value="MessageRejected"/>
 </xs:restriction>
 </xs:simpleType>
 <xs:simpleType name="TypeBPriority">
 <xs:restriction base="xs:string">
 <xs:enumeration value="AF"/>
 <xs:enumeration value="NO"/>
 <xs:enumeration value="OK"/>
 <xs:enumeration value="QA"/>
 <xs:enumeration value="QB"/>
 <xs:enumeration value="QC"/>
 <xs:enumeration value="QD"/>
 <xs:enumeration value="QK"/>
 <xs:enumeration value="QN"/>
 <xs:enumeration value="QP"/>
 <xs:enumeration value="QQ"/>
 <xs:enumeration value="QU"/>
 <xs:enumeration value="QX"/>
 </xs:restriction>
 </xs:simpleType>
 <xs:simpleType name="FaxServiceName">
 <xs:restriction base="xs:string">
 <xs:enumeration value="IPFax"/>
 <xs:enumeration value="BFax"/>
 </xs:restriction>
 </xs:simpleType>
 <xs:simpleType name="MessageStatusType">
 <xs:restriction base="xs:string">
 <xs:enumeration value="failed"/>
 <xs:enumeration value="relayed"/>
 <xs:enumeration value="received"/>
 <xs:enumeration value="delivered"/>
 <xs:enumeration value="rejected"/>
 <xs:enumeration value="re-injected"/>
 <xs:enumeration value="intercepted"/>
 <xs:enumeration value="drained"/>
 <xs:enumeration value="op-dropped">
 <xs:annotation>
 <xs:documentation>message dropped by an operator</xs:documentation>
 </xs:annotation>
 </xs:enumeration>
 <xs:enumeration value="sys-dropped">
 <xs:annotation>
 <xs:documentation>message dropped by the messaging system</xs:documentation>
 </xs:annotation>
 </xs:enumeration>
 <xs:enumeration value="odmci">
 <xs:annotation>
 <xs:documentation>out of date message cancellation input</xs:documentation>
 </xs:annotation>
 </xs:enumeration>
 <xs:enumeration value="odmco">
 <xs:annotation>
 <xs:documentation>out of date message cancellation output</xs:documentation>
 </xs:annotation>
 </xs:enumeration>
 <xs:enumeration value="other"/>
 </xs:restriction>
 </xs:simpleType>
 <xs:complexType name="AFTNDataType">
 <xs:attribute name="isDataCollect" type="xs:boolean" use="optional">
 <xs:annotation>
 <xs:documentation>To determine a Type B traffic chargeable</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="messageIdentifier" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation/>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="SMI" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation>Standard message identifier for Type B messages</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="doubleSignature" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation/>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="BATAPSN" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation>The BATAPSN number of a message</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="ISN" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation>The ISN number of a message</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 </xs:complexType>
 <xs:complexType name="TypeBDataType">
 <xs:attribute name="isDataCollect" type="xs:boolean" use="optional">
 <xs:annotation>
 <xs:documentation>To determine a Type B traffic chargeable</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="messageIdentifier" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation/>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="SMI" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation>Standard message identifier for Type B messages</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="doubleSignature" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation/>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="eopt" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation>eopt is 10 numeric characters long and the value is always 0000000000, Eric indicated his team does not populate any value in this field. </xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="documentConversion" type="xs:boolean" use="optional"/>
 <xs:attribute name="subject" type="xs:string" use="optional"/>
 <xs:attribute name="charSet" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation>The character set of a message body</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="BATAPSN" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation>The BATAPSN number of a message</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="ISN" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation>The ISN number of a message</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="cnxType" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation>The connection Type of a message</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="Location" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation>The location of a connection coming from</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 </xs:complexType>
 <xs:complexType name="SMTPDataType">
 <xs:attribute name="subject" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation/>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="doubleSignature" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation/>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="rule" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation/>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="resend" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation/>
 </xs:annotation>
 </xs:attribute>
 </xs:complexType>
 <xs:complexType name="TypeXDataType">
 <xs:attribute name="messageIdentifier" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation/>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="doubleSignature" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation/>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="documentConversion" type="xs:boolean" use="optional"/>
 <xs:attribute name="subject" type="xs:string" use="optional"/>
 <xs:attribute name="XATAPSN" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation>The XATAPSN number of a message</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="BadgerId" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation>The BadgerId to a Type X message is what ISN to a Type B message</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 </xs:complexType>
 <xs:complexType name="FAXDataType">
 <xs:attribute name="errorCode" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation>Error code for the request. 0=success.</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="errorString" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation>The error message, if any.</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="serviceName" type="tns1:FaxServiceName" use="optional">
 <xs:annotation>
 <xs:documentation>Enum value in FaxServiceType</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="channelNumber" type="xs:int" use="optional">
 <xs:annotation>
 <xs:documentation>The fax channel on the server.</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="receivedSize" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation>The size of the received message, including headers.</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="convertedSize" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation>The size of the message after conversion for fax.</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="totalSentSize" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation>The sum of the bytes sent, including cover pages and retries.</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="totalConnectTime" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation>The sum of time connected to a fax receiver for all attempts.</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="totalDuration" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation>The sum of the off-hook, or network time, for all attempts.</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="nbrFaxPages" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation>The number of pages in the message, including the cover sheet.</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="totalPages" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation>The sum of the pages sent for all attempts.</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="recvCSID" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation>The CSID received from the remote fax system.</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="tries" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation>The number of fax attmpts.</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="subject" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation/>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="acknow" type="xs:string" use="optional"/>
 <xs:attribute name="cod" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation/>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="referenceNumber" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation>The UFAX MSG_ID for the message.</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="distID" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation>The UFAX MSG_RQ_ID for the message.</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="fineResolution" type="xs:boolean" use="optional">
 <xs:annotation>
 <xs:documentation>True for Fine resolution, false for Coarse resolution.</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="baudRate" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation>The connection speed for the fax.</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="sitaReceiveTime" type="xs:dateTime" use="optional">
 <xs:annotation>
 <xs:documentation>The time when the message is received into SITA's network.</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="ufaxReceiveTime" type="xs:dateTime" use="optional">
 <xs:annotation>
 <xs:documentation>The time when UFAX receives the message, when it is delivered to the UFAX inbox.</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="startConversionTime" type="xs:dateTime" use="optional">
 <xs:annotation>
 <xs:documentation>The time when the Converter starts processing a message. If it takes more than one attempt to convert the message, this will be the time of the first attempt.</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="endConversionTime" type="xs:dateTime" use="optional">
 <xs:annotation>
 <xs:documentation>The time when the Converter completes the conversion process. If it takes more than one attempt to convert the message, this will be the time of the last attempt.</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="tfaTime" type="xs:dateTime" use="optional">
 <xs:annotation>
 <xs:documentation>The time of the first call attempt for the message. If UFAX is already calling the fax number for a different message, then this will be the time the message was queued for calling.</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="completionTime" type="xs:dateTime" use="optional">
 <xs:annotation>
 <xs:documentation>The time when the fax has been completed, either because the fax was delivered or it reached the maximum error threshold.</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="reportTime" type="xs:dateTime" use="optional">
 <xs:annotation>
 <xs:documentation>The time when the delivery report is sent. Not used if a report isn't sent.</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="doubleSignature" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation>For BFax, the Double Signature for the message if any.</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="userConfigType" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation>Legacy bit-mapped field for BFax.</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="networkAccessPoint" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation>The network access point where the channel was connected.</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 </xs:complexType>
 <xs:complexType name="OmhDataType">
 <xs:attribute name="msgIdent" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation/>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="sysMsgIdent" type="xs:string" use="required">
 <xs:annotation>
 <xs:documentation/>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="inMsgFmt" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation/>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="outMsgFmt" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation/>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="toDirection" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation/>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="fromDirection" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation/>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="inMsgSize" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation/>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="outMsgSize" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation/>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="compCode" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation/>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="applicationId" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation/>
 </xs:annotation>
 </xs:attribute>
 </xs:complexType>
 <xs:complexType name="AddressType">
 <xs:annotation>
 <xs:documentation>This is a generic address object</xs:documentation>
 </xs:annotation>
 <xs:simpleContent>
 <xs:extension base="xs:string">
 <xs:attribute name="responsible" type="xs:boolean" use="optional" default="false">
 <xs:annotation>
 <xs:documentation>Used to denote whether the address should be delivered or not, is the node responsible for delivery of this address</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="typeOfAddress" type="tns1:MessageType" use="optional">
 <xs:annotation>
 <xs:documentation>Type of the address we are given</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="mapped" type="xs:boolean" use="optional" default="false">
 <xs:annotation>
 <xs:documentation>Used to denote whether the address is mapped or not</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="masqueraded" type="xs:boolean" use="optional" default="false">
 <xs:annotation>
 <xs:documentation>used to denote if the address is masqueraded, this happens often when messages are pushed through gateways.</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 <xs:attribute name="masqueradedID" type="xs:string" use="optional">
 <xs:annotation>
 <xs:documentation>If the address is masqueraded than this is the place where I can carry the original address</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 </xs:extension>
 </xs:simpleContent>
 </xs:complexType>
 <xs:complexType name="HostType">
 <xs:annotation>
 <xs:documentation>This is a generic host object</xs:documentation>
 </xs:annotation>
 <xs:sequence>
 <xs:element name="HostName" minOccurs="0">
 <xs:annotation>
 <xs:documentation>Hostname of the server</xs:documentation>
 </xs:annotation>
 <xs:complexType>
 <xs:simpleContent>
 <xs:extension base="xs:string">
 <xs:attribute name="hostType" type="tns1:MessageType" use="optional">
 <xs:annotation>
 <xs:documentation>Type of the host such as MQ, JMS, SMTP etc</xs:documentation>
 </xs:annotation>
 </xs:attribute>
 </xs:extension>
 </xs:simpleContent>
 </xs:complexType>
 </xs:element>
 <xs:element name="NodeID" type="xs:string" minOccurs="0">
 <xs:annotation>
 <xs:documentation>Optional NODE ID goes here</xs:documentation>
 </xs:annotation>
 </xs:element>
 <xs:element name="HostIP" type="xs:string" minOccurs="0">
 <xs:annotation>
 <xs:documentation>Service or host IP address of the service</xs:documentation>
 </xs:annotation>
 </xs:element>
 <xs:element name="HostPort" type="xs:integer" minOccurs="0">
 <xs:annotation>
 <xs:documentation>Port address of the service</xs:documentation>
 </xs:annotation>
 </xs:element>
 <xs:element name="url" type="xs:string" minOccurs="0">
 <xs:annotation>
 <xs:documentation>URL address of the service</xs:documentation>
 </xs:annotation>
 </xs:element>
 <xs:element name="HostChannel" type="xs:string" minOccurs="0">
 <xs:annotation>
 <xs:documentation>Channel name of the service</xs:documentation>
 </xs:annotation>
 </xs:element>
 <xs:element name="ConnectionNumber" type="xs:string" minOccurs="0">
 <xs:annotation>
 <xs:documentation>the connection number that host is connecttng to.</xs:documentation>
 </xs:annotation>
 </xs:element>
 <xs:element name="CircuitNumber" type="xs:string" minOccurs="0">
 <xs:annotation>
 <xs:documentation>This is SITA's CNR</xs:documentation>
 </xs:annotation>
 </xs:element>
 <xs:element name="DestinationNumber" type="xs:string" minOccurs="0">
 <xs:annotation>
 <xs:documentation>This is SITA's DNR</xs:documentation>
 </xs:annotation>
 </xs:element>
 <xs:element name="X25DNA" minOccurs="0" maxOccurs="unbounded">
 <xs:annotation>
 <xs:documentation>This is SITA's X25 dan numbers</xs:documentation>
 </xs:annotation>
 <xs:simpleType>
 <xs:restriction base="xs:positiveInteger"/>
 </xs:simpleType>
 </xs:element>
 <xs:element name="MessageStatus" type="tns1:MessageStatusType" minOccurs="0" maxOccurs="unbounded">
 <xs:annotation>
 <xs:documentation>Users can put anything they want here</xs:documentation>
 </xs:annotation>
 </xs:element>
 <xs:element name="MiscData" type="xs:string" minOccurs="0" maxOccurs="unbounded">
 <xs:annotation>
 <xs:documentation>Users can put anything they want here</xs:documentation>
 </xs:annotation>
 </xs:element>
 <xs:element name="isCustomer" type="xs:boolean">
 <xs:annotation>
 <xs:documentation>False if the sender/receiver is a SITA system</xs:documentation>
 </xs:annotation>
 </xs:element>
 </xs:sequence>
 </xs:complexType>
 <xs:complexType name="SitaIdType">
 <xs:sequence>
 <xs:element name="sitaUID" type="xs:string">
 <xs:annotation>
 <xs:documentation>The unique ID assigned to the message by the first receiving system. This ID must be contained in the message.</xs:documentation>
 </xs:annotation>
 </xs:element>
 <xs:element name="TransactionID" type="xs:string">
 <xs:annotation>
 <xs:documentation>An identifier assigned or created for this event. This must be a unique identifier for this message, i.e. the combination of the SitaUID and transaction ID must be unique. This ID must be contained in the message.</xs:documentation>
 </xs:annotation>
 </xs:element>
 </xs:sequence>
 </xs:complexType>
</xs:schema>

On ME21N / ME22N / ME23N PUT SOME TAB INVISIBLE.

Hi,
I need put the text tab on this transactions me21n me22n and me23n INVISIBLE for some users, how can i do this?
tks.
Carlos Siqueira.

We had a requirement for hiding the tab Spec2000 in item detail.
The code in the enhancement implementation AD_S2K_SUB_LMEGUIU08 in function module MEGUI_BUILD_PO_ITEM_PLUGIN was commented out to remove the extra tab as the structure that is linked to this tab was MEPO1339.
May be the same works for you for the other tab.

ALE , EDI and IDOC with MM??

hii
What is ALE, EDI and IDOC in SAP??
How its linked with MM??
Explain the above things with example
Thanks

Hi!
IDOC = Intermediate Document
IDoc or Intermediate Document is a standard SAP document format. IDoc's allow different application systems to be linked via a message-based interface.
For more detailled information look in SAPNET under
http://service.sap.com/EDI
For exapmle in purchasing:
The IDoc message type ORDERS is used to send a purchase order to a vendor.
EDI = Electronic Data Interchange
EDI stands for Electronic Data Interchange, which means that data is electronically transmitted from one system to another. The main requirement of EDI is that the systems of the communicating partners understand each other. Usually, the data from one partner gets mapped into the format of the other partner and vice versa.
Supporting this there exist EDI standards (named EDIFACT, ANSIX12, ODETTE, VDA, TRADACOMS, SPEC2000, ...), where the data formatting for exchanging documents are specified. Normally the partners agree using a special standard message (for example EDIFACT message ORDERS for a purchase order).
In the SAP system the outgoing data are stored in IDoc format. When processing a receiving document, the Inbound SAP system receives the data in IDoc format too.
Further processing (converting/mapping from IDoc in another format and vice versa) depends on the partner agreement:
If the partners have agreed using a special EDI standard, mapping between IDoc and the EDI standard is necessary. This mapping is not supported by SAP, external converters or EDI subsystems must be installed by the customers for this purpose.
If both systems use SAP software, there is usually no need for mapping (which can save users a lot of money). The two systems are often connected via ALE (Application Link Enabling).
If partners are using XML, the SAP Business Connector can be used. The business connector is a tool used to help customers connect via EDI. It includes routing and mapping and is XML compatible. To read more about XML at SAP go to SAPNet Alias 'XML' (http://intranet.sap.com/XML).
For example:
Vendor can send the invoice by EDI creating an IDoc with message type INVOIC using IDoc Type INVOICxx. He can determine (depending on the partner agreement) how to create an IDoc for Inbound processing with FI or MM-IV.
ALE = Application Link Enabling
ALE is short for Application Link Enabling. Special Basic programs support this functionaliity (see documentation of BC_MID_ALE).
To link applications you have to configure an ALE model. It contains all relevant data about how a system's configuration (normally a central system and assigned local systems) exchange data.
With help of the ALE technology, the distribution of contracts is possible in MM via the following business process:
Contracts that a central purchasing organization distributes to local purchasing organizations to allow the latter to utilize the more favorable conditions they contain for the procurement of materials or external services.Each local purchasing organization sends information on its own release orders back to the central purchasing organization.
For this purpose the contract in the central system can be copied to the local systems (with message BLAORD and COND_A). When a release order to a distributed contract is created in a local system, the release docu is automatically sent to the central system (with message BLAREL) updating the release docu of the contract in the central system.
Precondition for this scenario is, that in all systems the used master data (material, vendor, sources of supply, ...) are the same. This master data can be distributed by ALE, which should be done before sending the contract from the central system. Available message types for distribution of master data are:
MATMAS (ARTMAS in retail system) for material master
CREMAS for Vendor master
INFREC for info record
SRCLST for source list
COND_A for conditions of info record
SRVMAS for service master data
Technical documentation to ALE can be found by path:
Basis Components / Middleware (BC-MID) / Application Link Enabling (BC-MID-ALE)
The most important Transactions for testing Idoc:
WE02 Display IDOC
WE05 IDOC list
WE19 Testing IDOCs
BD87 Status Monitor for ALE Messages (reprocess)
Notes:
456127 FAQ: Electronic Data Interchange (EDI) in Purchasing
536411 Sample scenario for ALE contract distribution (only internally released)
I hope I could help you fruther
Best regards
Erika

Error:IDoc cannot be processed: Qualifier not supported.

Hi experts,
                         I got this error when executing the idoc
message type: dirdeb
basic type : pexr2003
error:Error during creation of internal payment order.
IDoc cannot be processed: Qualifier not supported.
Thanks
Saravanaperumal N

Hello,
001     Customer Purchase Order
002     Vendor Order
003     Customer Inquiry
004     Vendor Quotation
005     Customer Contract Number
006     Vendor Contract Number
007     Collective Number for Quotations
008     Last Purchase Order Number (SPEC2000 Acknowl.)
009     Invoice Number
010     Internal Number (Document)
011     Referenced Document Number
012     Delivery Note Number
013     Internal PO Number
014     Accounting Document
015     Billing Document Number of Invoicing Party
016     Number of Preceding Document
017     Assignment Number
018     Customer Order Number
019     ISR Number
020     Invoice List Number
021     ID for Cost Assignment
022     Payment Document Number
023     Banker's Acceptance
024     Matured Certificate of Deposit (CD)
025     Loan
026     Check Number
027     Foreign Exchange Contract Number
028     Credit Memo
029     Payment Advice Note Number
030     Original Purchase Order Number (ALE)
031     Return Leg Number
032     Reference Bank
033     Third-Party Reference Number
034     Reference Number of Beneficiary's Bank
035     Message Reference
036     Credit Card Number
037     Statement Number
038     Account Statement No. (Deposit No.)
039     Account Statement No. (Deposit Seq. No)
040     Payee Code
041     MICR Line
042     Imported Line
043     Vendor Contract Number
044     Ship-To Party's PO Order
045     Cost Center
046     Profitability Segment No.
047     Work Breakdown Structure Object
048     Profit Center
049     Business Area
050     Delivery Order
051     Delivery Order Route Number
052     Sequence Number
053     Scheduling Agreement Number
054     External Transaction
055     Promotion Number
056     Customer Quotation Number
057     Customer Buying Group
058     Customer Contract Number
059     Check Number from Check Register
060     JIT Call Number
061     Internal Delivery Note Number
062     Customer PO no. for consignment issue by ext. service agent
063     External Delivery Note Number
064     Goods Receipt/Issue Slip Number
065     Repetitive Wire Nummer
066     External Order Number
067     Quality Notification Number
068     External Inquiry Number
069     Business Partner Reference Key
070     Reference Text for Settled Items
071     Customer ID no.
072     Agreement Number
073     Credit Advice Number
074     Transfer Number
075     Check Number
076     Credit Posting Number
077     Transfer number (just transferred)
078     Delivering Profit Center
079     Batch Number
080     Certificate Profile
081     Collective Daily Delivery Note
082     Summarized JIT call
083     External Delivering Plant
084     Tax Number Tax Office §14
085     KANBAN ID
086     Kanban Control Cycle
087     Reference Document Number Billing Doc.
101     Resale Invoice No.
102     Resale Ship and Debit Agreement No.
103     Customer Claim Reference Number
104     Design Registration Number
105     TPOP Order Number
106     TPOP Reference Order Number
111     Partner Business Area
APY     Approval Year of Official Document Numbers
APN     Registration Number of Official Document Numbers
SNC     Serial Number of Statement
These are all the Value range for qualifier, use which one suits your requirement
Regards,
Abhishek

Create massive attachments list to an order

Hi experts,
I would like to create a massive attachment list joined with an order. It could be a Word, Excel, Image, PDF, ... document.
Maybe, best solution would be having all the BOR objects upload in a server location. Then I would have to vinculate the order with the document path.
First I try to reach this using legacy transaction LSMW but I've got the limitation that the button attachment list dissapears when recording.
Which way I can reach my objective? Any ideas?
Lots of thanks,
Javier

Hi,
The new sales document number gets populate in E1EDK01-BELNR.
The existing order ( reference order ) gets populated in E1EDK02-BELNR.
In E1EDK02, there are different qualifier for different referece doc type. They are
'001' Customer purchase order
'002' Vendor order
'003' Customer inquiry
'004' Vendor quotation
'005' Customer contract number
'006' Vendor contract number
'007' Collective number for quotations
'008' Last purchase order number (SPEC2000 Acknowl.)
'009' Invoice number
'010' Internal number (document)
'011' Referenced document number
'012' Delivery number
'013' Internal PO number
'014' Accounting document
'015' Billing document number used by presenter of invoice
and many more.
Go to transaction WE60, enter obj name = 'ORDERS05' and hit 'F8. It will display IDOC hierarchy. Look at the structure of segments E1EDK01, E!EDK02 and all other segments. You will have better idea.
Let me know if you need any other information.
Regards,
RS

Enhancment on ME21N

Hi Experts,
while creating po using me21n i need to validate the delivery date with document date,
will you plz provide any enhancment spot or badi's or user exit to do this.
thanks,
taj

We had a requirement for hiding the tab Spec2000 in item detail.
The code in the enhancement implementation AD_S2K_SUB_LMEGUIU08 in function module MEGUI_BUILD_PO_ITEM_PLUGIN was commented out to remove the extra tab as the structure that is linked to this tab was MEPO1339.
May be the same works for you for the other tab.

Turn off tab on PO Item screen

I am working with ECC6.0. I want to hide a tab on the PO Item sreen called SPEC2000. Can I use one of the BADI's to do this? Please provide details.

I have solved this on my own.

SPEC2000

Similar Messages

Maybe you are looking for