EDI Text Configuration

Hi All,
Anyone try to answer this.
How can i configure the Text in Vendor :Control data.
I am providing the path for it.
Go to change Vendor transaction - Enter Vendor and Company Code - Select "Control" option in "General Data".
When you go to "Change Vendor: Control" screen, go to "Extras" top menu and Select "Texts". I need to know how we can configure that text.
Actual Problem
Some one has configured the EDI text fields here. These text fields are visible through FK03. When i try to view the same text field through MK03, it is not visible. Please let me know the exact configuration area
Thanks

To view via MK02 you need authorization, talk to basis guy.
to configure this text you need to go
SPRO-MM-Purchaisng-Vendor master-Define Text Types for Central Texts

Similar Messages

  • Seeburger EDI Text to EDI XML conversion failure should throw an error

    Hi,
    I am expecting an error message to be thrown when EDI Text to EDI XML conversion fails at Message splitter of Seeburger module. I am getting the following error in the log.
    "2012-01-19T01:46:08.032-0800 ERROR [Error:ID=2150;LEVEL=3] counter value (41) of incoming field (UNB.UNH.UNT:0074) doesnt match the calculated value (39).
    DESCRIPTION: Either the counter value is not filled in the source file or the counter field value is wrong. "
    But my expectation is that the channel should show some error in Adapter Engine monitoring itself. As shown below, it is just showing some warning that because of above error, it is not creating the attachment. Now I am expecting the the following warning to be an error rather than just warning. Please let me know if any idea on the same.
    19.01.2012 01:46:08 Information SEEBURGER/MESSAGESPLITTER: Trying to establish CCI Connection to Message Splitter Adapter
    19.01.2012 01:46:08 Information SEEBURGER/MESSAGESPLITTER: Creating CCI Interaction
    19.01.2012 01:46:08 Warning SEEBURGER/MESSAGESPLITTER: There is no attachment to split. So there is nothing to do.
    19.01.2012 01:46:08 Information SEEBURGER/MESSAGESPLITTER: Finished splitting!
    BR,
    Aman

    Thanks you all for your inputs..
    I got the solution for the same.
    I need to set the mapping program name specifically rather than AUTO for bic mappingName parameter. This has turned my communication channel status in RWB into Red for errors.
    Closing this thread ...
    Regards,
    Aman

  • Which table stores the Sales Order--Header--Texts--EDI Text?

    Hi Experts,
    I hv a requirenment regarding the Sales Order -> HEADER -> TEXTs -> EDI Text-Int, so, I need to hv some Orders(#). which does hv this text on them, for as test data.
    So, I am looking which table stores, this text for my_sales_oders_12345678.
    [ actually, i got some info from sdn, like,
    Table TTXOB -> stores Texts: application object for Sales order header it is always VBBK i.e. field TDOBJECT = VBBK.
    Now all the text types i.e. text ids are stored in table TTXID
    So fetch all text ids(TDID) from this table based on TDOBJECT = VBBK. And its descriptions are stored in TTXIT table.
    but, no use this ]
    thanq
    Edited by: Srinivas on Jul 10, 2008 11:06 PM

    Hi Srinivas,
    Generally to access the text we use READ_TEXT function Module.
    we need to pass the four parameters
    ID
    LANGUAGE
    NAME
    OBJECT
    You can find these parameters in the sales order it self.
    Goto ---> Header ---> Texts
    Now double click on the text it takes you to the Text Editor. You can find the screen Display Form Header . In this goto Menu Path Goto ---> Header. You get a screen Text header. Here you can find the these parameters.
    Text Name
    Language
    Text ID
    Text Object
    You need to pass these parameters to the function Module to text the text.
    You can also fins the text in Table STXH
    Best regards,
    raam

  • Material Text Configuration

    Hi All,
    Can anybody help me with the following.
    Is there any configuration setting for PO text type. I am able to see TEXT configuration setting for Vendor, RFQ, PO etc but i am not able to find any for a Material text configuration. Does anything exist as such. Please help me out.
    Thanks

    well i am also tried doing the same process myself but without abaper it is impposible anywyas lets go step by step
    suppose we have some zfields and we want to make a subscreen and then a view for that
    these 1 to 3 steps has to be done by abaper or a techno functional
    1> create a function module using the create programme option in configure material master & whicle creating it use the standrd function module for that u can get the name of those from f1 help in adjacent to the create programme button
    i belive u have cpied a fuction module
    2> now go to se38 and copy a satndard progrrame into your programme (copy the programme mentioned in fornt of the subscreen in any view )
    3> go to screen painter and create the fields in there and map the coding and table with that
    i hope your subscreen is ready for use
    4> go to the tcode OMT3B and copy a previously created screen sequence as i suggest not to change any standrd one
    5> select your screen sequence suppose z1 and click on the data screen folder then selct the purcahsing view and then click onthe subscreen folder then in the last row gassign your subscreen code
    i hope u will be proced further
    if any doubt then communicate

  • EDI & IDOC Configuration

    Hi Friends
    Any body please help me to my questions.
    1) How to configured to EDI (Send idoc to third party Aramex).
    2) What is the process code for Betmas01 IDOC.
    3) How to raise idoc automatically when we create a data on sitemaster. (Betmas01).
    Thanks
    Krishna

    Hi krishna,
    welcome to SDN
    Configuring EDI Integration
    BEA WebLogic EDI Integration must be completely configured before it can be used. Because EDI Integration depends on BEA EDI Connect for WebLogic Integration to operate properly, make sure you configure Power.Enterprise! correctly so that you can communicate with your trading partners.
    General Configuration
    This section discusses the general configuration information that you should perform before attempting to configure a specific document exchange with a trading partner.
    Configure Trading Partners
    Before configuring individual transactions, you should configure all trading partners, including your own company, using Power.Manager!. For more information about configuring trading partners, see the following topics:
    Configuring Trading Partners
    Chapter 4, "Partners," in the Power.Manager! User Reference Manual
    Configure VAN/Trading Partner Connectivity
    You should also configure your trading partner connectivity before attempting to configure individual document exchanges. See the following topics:
    Connections and VAN Connectivity
    Chapter 3, "Connections," in the Power.Manager! User Reference Manual
    Although you may not want to set up connectivity to your production trading partners at this time, you may want to configure them with file connectors for development and testing purposes.
    Configuring EDI Integration to Receive an EDI Document
    This section describes how to configure EDI Integration so that the BEA WebLogic Adapter for Power.Enterprise! 3.1 can receive an EDI document and send it to the WebLogic Integration process engine as an XML document.
    Pre-Planning
    Determine the EDI standard, version, and document type of the document you will receive. For example, you might select an X12 850 document v4010, which is an X12-standard, 850-type document, version 4010.
    Define the XML format that you will use internally. This XML format should contain a complete data map of the fields in the EDI document that you will use.
    Create a DTD and an XSD for the XML document. You must create both because Power.Enterprise! and WebLogic Integration do not use the same data file format for this step. WebLogic Integration requires an XSD (if you supply one at all), while Power.Enterprise! requires a DTD. You should note that Power.Enterprise! does not provide any export utility to export a DTD or XSD from a map definition once the DTD or XSD has been imported. You will be responsible for creating both the DTD and XSD files.
    Within Power.Enterprise!
    Create a map between the XML document and the EDI document. Import the DTD into Power.Map! to load the XML document standard. The appropriate EDI document should already exist in the Power.Server! repository. If the EDI document is not present, contact BEA Customer Support. For more information about how to do this, see the following topics:
    Mapping XML and EDI Data
    Chapter 3, "Maps" in the Power.Map! User Reference Manual
    Define an inbound connection. This connection should use your trading partner's connection protocol, which you should have defined already. For more information, see Connections and VAN Connectivity.
    Define an RMI target connection. This connection is used to communicate with the WebLogic Integration process engine.
    Define an exchange profile, using the procedure discussed in Configuring Exchange Profiles. This exchange profile should connect the inbound connection from your trading partner to the RMI target connection.
    Within BEA WebLogic Integration
    Create an application view, using the procedure in Configuring the BEA WebLogic Adapter for Power.Enterprise!.
    Create an event for the application view you just created, using the procedure in Configuring Events. Be sure to set the following parameters:
    Event Name: A descriptive name for the event, such as ReceivePurchaseOrder
    Event Description: Text that provides details about the event
    RMI Service Name: Should match RMI service name defined in the Power.Enterprise! RMI target connection set up in the Within Power.Enterprise! section
    XSD: The XML schema of the XML message to be received (optional)
    XML Root Element: The XML root element of the XML schema (optional)
    Deploy the application view you have created and defined.
    Verify that the Power.Server! instance is running. At this point, the application view should be available to the WebLogic Integration process engine through the application integration plug-in. For more information about the application integration plug-in, see Understanding the Application Integration Plug-In for BPM in Introducing Application Integration.
    Note: Always start the Power.Server! before you start WebLogic Integration or WebLogic Server. The WebLogic Integration connectors expect to see the Power.Server! running when they are initialized, and they throw exceptions if Power.Server! is not running when they are initialized.
    Configuring EDI Integration to Send an EDI Document
    This section describes how to configure EDI Integration to send an EDI document using an XML document in the WebLogic Integration process engine as the source.
    Pre-Planning
    Determine the EDI standard, version, and document type of the document you will receive. For example, you might select an X12 850 document v4010, which is an X12-standard, 850-type document, version 4010.
    Define the XML format that you will use internally. This XML format should contain a complete data map of the fields in the EDI document that you will use.
    Create a DTD and an XSD for the XML document. You must create both because Power.Enterprise! and WebLogic Integration do not use the same data file format for this step. WebLogic Integration requires an XSD (if you supply one at all), while Power.Enterprise! requires a DTD. You should note that Power.Enterprise! does not provide an export utility that can be used to export a DTD or XSD from a map definition once the DTD or XSD has been imported. You are responsible for creating both the DTD and XSD files.
    Within Power.Enterprise!
    Create a map between the XML document and the EDI document. Import the DTD into Power.Map! to load the XML document standard. The appropriate EDI document should already exist in the Power.Server! repository. If the EDI document is not present, contact BEA Customer Support. For more information about how to do this, see the following topics:
    Mapping XML and EDI Data
    Chapter 3, "Maps" in the Power.Map! User Reference Manual
    Define an outbound connection. This connection should use your trading partner's connection protocol, which you should have defined already. For more information, see Connections and VAN Connectivity.
    Define an RMI source connection. This connection is used to communicate with the WebLogic Integration process engine.
    Define an exchange profile, using the procedure discussed in Configuring Exchange Profiles. The exchange profile should connect the RMI source connection to your trading partner's outbound connection.
    Within BEA WebLogic Integration
    Create an application view, using the procedure in Configuring the BEA WebLogic Adapter for Power.Enterprise! in this document.
    Create a service for the application view you just created, using the procedure in Configuring Services in this document. Be sure to set up the following parameters:
    Service Name: A descriptive name for the service, such as SendPurchaseOrder
    Service Description: Text that provides details about the service
    Connection Name: Should match the RMI service name defined in the Power.Enterprise! RMI target connection set up in the Within Power.Enterprise! section.
    XSD: The XML schema of the XML message to be sent (optional)
    XML Root Element: The XML root element of the XML schema (optional)
    Deploy the application view you have created and defined.
    Verify that the Power.Server! instance is running. At this point, the application view should be available to the WebLogic Integration process engine through the application integration plug-in. For more information about the application integration plug-in, see Understanding the Application Integration Plug-In for BPM in Introducing Application Integration.
    see this link for complete edi information
    http://msdn.microsoft.com/en-us/library/bb246069.aspx
    for your second question......
    sapsdforum.files.wordpress.com/2008/03/idoc_handy_doc.pdf
    Assigning a Process Code (Direct Inbound Processing)
    This section describes how to assign a new process code to the new function module. This enables the function module to be identified from the partner profiles defined in the IDoc Interface when an IDoc of the new message type is received.
    Prerequisites
    You must have completed the required steps in Defining and Using a Basic Type .
    Procedure
    Choose SAP Menu ® Tools ® IDoc Interface/ALE ® Development ® Inbound Processing ® Process Code (WE42), or navigate to Inbound Processing Process Code, then  and New Entries.
    Enter your process code and a description. Choose the Processing with ALE and Processing by function module options and save your entries.
    The maintenance screen is displayed (either automatically or manually), in which you can assign the inbound function module to the process code.
    Choose New entries and enter in the detail screen:
    Your process code
    Module (inbound) frame: Your function module and the maximum number of attempts permitted for posting the application data before exception handling is triggered.
    IDoc frame: Your object type, the trigger event inputErrorOccurred and the completing event inputFinished.
    Application object frame: Your object type
    Leave the other fields blank. Save your entries and return to the process codes inbound initial screen.
    Go back using  to maintain the inbound process codes and choose the Logical message navigation.
    In change mode choose New Entries.
    Enter the message type (logical message) and the process code and save your entries. As a result, the possible entries (F4) in the partner profiles can display the possible process codes from the logical message, that is, the business view.
    If you chose all types in the last step, the value help displays the process code for all message types. This is also valid for both other options for message type and function.
    Result
    This assignment has specified a new process code for the function module. You can now enter this process code in the partner profiles.
    Make the following entries for the example:
    Process code
    TESTEIN
    Basic type
    TESTER01
    Function module
    IDOC_INPUT_TESTER
    Maximum number of attempts
    0
    Message type (logical message)
    TESTER
    IDoc object type
    IDOCTEST
    Application object type
    BUS2032 (sales order)
    To generate Partner profiles automatically you may use BD82 or go to BD64
    thanks'
    karthik

  • Seeburger AS2/EDI sender configuration details

    Hello All,
    I  am working in EDI interface for ANSI X12 using Seeburger AS2/EDI , As I am new to B2B interface I have one doubt regarding Transaction set identifier code,interchange sender and receiver ID  , In case of B2B add on it is clearly configured on EDISeparator Sender Adapter  under filter
    but in case of Seeburger AS2/EDI I am not understanding where we can add this details ,
    Thanking you
    Sridhar

    Hello Sridhar,
    for incoming data, the Seeburger BIC-Adapter uses a mapping in the Module-Chain which automatically detects the following parameters
    - MessageType and Version  (e.g. ANSIX12_850_V4010) from ST segment
    - Interchange Sender ID (from ISA segment)
    And the MessageSplitter then allows to forward each combination to a specific SenderAgreement for processing the data in PI.
    This example shows an entry in the "MessageSplitter" that assigns an 850 V4010 message from a partner with the Sender ID 11111111111  to a specific SenderAgreement to process the data...
    Kind Regards
    Stefan

  • EDI IDOC Configuration steps

    Hi,
    Can anyone provide me the step by step configuration of EDI IDOC ofr both incoming and outgoing mainly for PO.
    Thanks
    Regards,
    Srivatsan

    hi,
    Refer  SAP Note No. 455140  
    Refer  SAP Note No. 546147  
    Refer  SAP Note No. 607108  
    Refer  SAP Note No. 779972
    May be it will help you
    Thanks & Regards,
    Kiran

  • EDI Basic configuration settings for Third party sales

    Dear All,
    Could you help step by step how to configure EDI to send PO automatically to outsourcing company for the Third party sales order.
    Thanks
    CG Balaji

    Hi roberto
    Please send me basic EDI configuration document to my mail id [email protected] this will help me a lot.
    Thanks and regards,
    CG Balaji

  • B2B EDI File Configuration Settings

    Hi All,
    We are seeing some default values in our EDI files for following Segment elements.
    Interchange Control Number (100000044)
    Group Control Number (1044)
    We are using 4010_850 format.
    Let us know where to change these default values in B2B console.
    Thanks,
    Sid.

    Hi Sid,
    it's not default value. instead it is a running number automatically generated by B2B. it increments for ever interchange/group/transaction
    Thanks,
    Prasanna

  • Text configurations with sap-config-mode

    Would somebody explane to me:
    I changed text with url-parameter sap-config-mode=x in FITE_VC_GENERAL_DATA view in logon language (that's not EN or DE). The result after savig this change is that the English or German text are replased with numbers. For example I change text "Reason" of Feld-ID: CUSTOMER. When using language-parameter=EN, this text is shown as number "19". So there is no possibility to run travel application in English (or German) along with local language.
    I would like to know, is this standard behaviour? What's the point here? Whow must I make text-changes in application FITE_EXPENSES to be able top run it in local language as well as in English?
    Regards Seppo

    Hello P,
    Try transaction SOTR_EDIT. Choose Short text, Language and Text, this works with asterisk before and after your keyword (try location).
    With Display you'll find all packages where text location is used, first and foremost PTRM_WEB_UI.
    After choosing the text in screen OTR: Change Concept choose Edit-Context-Change, pass with enter Context-popup.
    You may also go straight to context-text from the component view. Transaction se80, package PTRM_WEB_UI, web dynpro component, for example FITE_VC_GENERAL_DATA, in Layout tab sheet activate the text, you aim to change, in Property-window double-click the field text $OTR:...-link, and you'll have the context-window, where you can modify the text.
    Check also this link: https://cw.sdn.sap.com/cw/docs/DOC-13926.
    BR
    Seppo

  • Reading EDI Text file

    Hi,
    I am
    Edited by: Amar J on Dec 3, 2010 2:02 PM

    hi,
    i am planning to acheive it through forms and to make use of text_io package.
    But problem with my plan is : is the delimiter so i have a line in the text file like
    MMX:ADD1:ADD2:ADD3 format.
    the actual data is ike
    MMX:Bank street:no:32:tel:050142563
    my task is to store all the fields(MMX,Bank Street,no:32,Tel:050142563) except the delimiters i have to store all the values.
    so with respect delemiter i cannot cut the data. how can solve this issue.in other words how to get the data based the delimiter if the data itself contains delimiter as a value.
    Please help me..
    Thanks..

  • Steps to configuring log4j with plain text file

    can anyone help me with the steps involved with configuring log4j with a plain text configuration file...Where should log4j.properties file be stored?.....do you have a simple example of a config file using a file appender?.....do I have to make changes within the startWebLogic.cmd script?.....Is it possible for you to lay out the procedure for me to begin logging?.....nothing I have tried thus far has worked.....Any help you may be able to provide will be greatly appreciated.

    i am using sun jsf implementaion version 1.2
    can i know do we need to specify anything for application bean to be called. beacause when i tried to print in sample application also my log was not getting printed.
    i have mentioned in my managed bean
    <managed-bean>
    <managed-bean-name>ApplicationBean1</managed-bean-name>
    <managed-bean-class>webapplication3.ApplicationBean1</managed-bean-class>
    <managed-bean-scope>application</managed-bean-scope>
    </managed-bean>
    i my page class
    protected webapplication3.ApplicationBean1 getApplicationBean1() {
    return (webapplication3.ApplicationBean1)getBean("ApplicationBean1");
    can i know why it is not getting called.

  • Oracle Text/Oracle Internet File System Installation/Configuration

    Hi,
    I have installed Oracle9i Database v9.0.1.0.0 on Linux. I would like to install Oracle 9i Internet File System as well. In the Oracle Internet File System pre-installation process, the pre-requisite for installing this is Oracle Text ( but optional ). How do I know that Oracle Text has been installed in the Oracle Universal Installer? If Oracle Text is installed, what is the best way to find out, it is configured properly?
    Why am I asking this is, when I install Oracle Internet File System, I'm getting an error
    "Unable to verify Oracle Text configuration. The following error occured:
    oracle.ifs.utils.action.ActionFailedException : Oracle Text seems to be misconfigured".
    Please help.
    Thanks
    Sriram

    I think the problem is your database configuration.
    You can reconfigure your database, it will hellp your database
    have Oracle Text .
    Before that, you need use Universal Installer, In Installed Products Tree, sure that you see
    Oracle Text in the Oracle Database 9i node.

  • Re : Inter company stock transfer through EDI

    Hi
          How to do the intercompany stock transfer through EDI. In this if Purchase order is created from one comapny a sales order should created automaticall in another Company. Fot this what is the SPRO settings.
    How to do this.
    Thanks
    Anto

    Hi,
    continues from here,
    Inbound file:     edi_in
    Function module:     See text below.
    Status file parameters
    Directory:     /home/edi/<portname>/
    Outbound file:     status.idoc
    Function module:     Leave blank if using above
    u2022     Both the portname and the exchange directory should be created according to the same naming convention. However, the portname should be in upper case whereas the corresponding directory name should be in lower case (see examples below).
         Portname (upper case):
                             <portname>
         Exchange directory name (lower case):           
                             /home/edi/<portname>
         where <portname> consists of:
         EDI<system name><client number><id char>
         <system name> is the name of  system on which port exists eg.      F01, PG1 etc.;
         <client number> is name of client on system which will use this      port; and
         <id char> is a single alphabetical character such as u2018au2019,u2019bu2019 etc.      typically,      u2018au2019 will denote dynamic outbound file naming (used      for testing) whereas      u2018bu2019 will denote static outbound file naming.      All ports will use static       inbound filenames.
    For example, the name of a port using dynamic file naming on system F01, client 610 would be named EDIF01610A.  The exchange directory would be named edif01610a. Similarly, the name of port using static file naming on system PG1, client 600 would be EDIPG1600B. The exchange directory name would be edipg1600b.
    Note that the function u201CEDI_PATH_CREATE_USERNAME_DT_TMu201D  can be used in the u201CFunction moduleu201D field  of the Outbound file parameters if IDocs are to be written to multiple files. In this case, the corresponding outbound filename field should be left blank. The standard IDoc exchange interface between the SAP EDI component and the EDI subsystem uses a single file for each transfer direction. However, should the exchange interface change, or for testing purposes, the function modules for dynamic naming can be used.
    2.4.2.     Control of EDI processes in R/3
    2.4.2.1.      Maintain: Outbound Process Code (WE41)
    IMGCross-Application ComponentsALE Extensions  Outbound
    Check that the outbound EDI processes in the R/3 system are defined.  Indicates which ABAP/4 function module to execute in order to create an outbound IDoc.
    The following assignments are available for R/3:
    2.4.2.2.      Maintain: Inbound Process Code (WE42)
    IMGCross-Application Components  ALE  Extensions  Inbound
    Check that the inbound EDI processes in the R/3 system are defined.  Indicates what kind of inbound processing to execute.
         A long list of options is available under Processing by function module, relevant ones are:
    INVF     INVOIC FI     Invoice receipt (Financial Accounting)
    INVM     INVOIC MM     Invoice verification (Mat Management)
    ORDC     ORDCHG     Change customer order
    ORDE     ORDERS     Create customer order
    ORDR     ORDRSP     Purchase order confirmation
    2.4.2.3.      Control: System Process Codes (WE40)
         Choose Processing by task.  Check that the codes indicating the type of EDI processing error are defined.  The only valid entries are the entries shown on the screen, as they are directly called via the EDI basis module.
    2.4.2.4.      Control: Status maintenance (WE47)
         Check that the codes indicating status of IDoc processing are defined.  The status values for outbound IDocs are between 01 and 39, while the status values for inbound IDocs begin with 50.  These values are delivered by SAP and cannot be customised.
    2.4.2.5.      Control: Partner Types (WE44)
         Check that the codes that identify the commercial relationships between the receiver and sender are defined.  Values are delivered by SAP.  Names of the programs and routines that validates the entry of the EDI trading partner ID:
    Partner type     Report name     Form routine
    B - Bank     RFETESTP     READ_T012
    KU - customer     RSETESTP     READ_KNA1
    LI - vendors     RSETESTP     READ_LFA1
    LS - logical system ( ALE)     RSETESTP     LOGSYS
    2.4.2.6.      Control: Forward Inbound (WE45)
    Allows for the forwarding of IDocs to a specific application.  Contains the exactly defined destination of an inbound IDoc within the SAP system.  Usually no changes are required.
    2.4.2.7.      Control: Status Process code (WE56)
    Choose Processing by task: The following set-up has been provided as default:
    Process code:     EDIS
    Identification:     TS30000078
    Description:     EDI-IDoc  status record processing
    The process code is for inbound status, The ID type is an identification code for inbound processing method (workflow or standard task) of the status record.
    3.     MM IMG CONFIGURATION
    3.1.     Global settings (IMG):
    3.1.1.     Units of measure (IMG  Global settings):
    The ISO code is important for EDI.  It is used to convert the internal SAP units of measure into standard units.
    The MM configurer must link the Unit Of Measure, EACH, with the ISO code PCE (Piece).
    3.2.     Link Schema to Purchase order
    Check the following:
    IMG  MM  Purchasing  Message determination  Message determination  Message Schemas
    Execute transaction u201CDefine Message Schemas for Purchase Orderu201D
    Select  transaction: Assign Schema to purchase order
    Add:      Usage =B for output
         Application = EF for purchase order
         Procedure = RMBEF1 for purchase order
    3.3.     Link application to EDI interface via message control:
    IMG  MM  Purchasing  Messages  Output Control
    Check following under Output Control:
         Condition table
         Access sequence
         Message types
         Message schema
         Output control
    3.4.     Enabling Multiple Output for Purchase Orders (Optional)
    For example: EDI & Printing
    IMG  MM  Purchasing  Message determination  Message determination Access sequence
    u2022     Create new access sequence (e.g. ZPUR), copy the access sequence 0001 but leaving the ''E'' flag blank (Exclusive is off). (Transaction M/50)
    u2022     Goto Define message types  maintain message types:
         Create a new message type (e.g. NEU1), setting the output type to 1 for printed output and using ZPUR as access sequence. (Transaction M/34)
    u2022     Goto Message Schema  define message schema  maintain output determination procedure:
         Update procedure RMBEF1 by adding a step for the new condition type (e.g. NEU1) prior to the standard delivered step for NEU. (Transaction M/36)
    u2022     Goto Processing program  Define Processing program  Output program: Purchase Order.
         - Add a NEU1 record to table TNAPR.  The program FORM Routine and layout must be specified.  (Copy an existing NEU record). (Transaction OMTB)
    u2022     Goto Processing program  Define Processing program  Output by partner type.
         - Add NEU1 record for VN (vendor). (Transaction OMTG)
    3.5.     Link Output type (fax=2, E-mail=7) to NEU (Purchasing)
    IMG  MM  Purchasing  Message determination  Message determination Access sequence
    u2022     Goto Processing program  Define Processing program  Output program: Purchase Order.
         - Add another NEU record to table TNAPR with the appropriate output medium. Copy an existing NEU record. (Transaction OMTB)
    u2022     Goto Processing program  Define Processing program  Output by partner type.
         - Add NEU record for VN (vendor). (Transaction OMTG)
    4.     SD APPLICATION REQUIREMENTS
    Assumption: SD is only used for testing purposes and configuration is based on a need basis - only configure the minimum.
    Reference SAP Course manual Chapter 11.
    4.1.     EDI Configurations
    4.1.1.     Conversion of SAP item categories to IDOC item categories (VOE1)
    IMG  S&D  EDI  EDI Messages  Conversion of SAP item categories to IDOC item categories
    Add the following entry:
    For Standard Item description :     0     OR     LDN
    Typically error message: ''Transaction LDN is not defined".
    4.1.2.     Partner functions
    IMG  S&D  EDI  EDI Messages  Configure EDI Partners Partner  Application  Partner function
    Check that the following partner functions exist: (at least)
    SP     Sold-to party
    VN     Vendor
    BP     Bill-to party
    SH     Ship-to party
    Note - the German abbreviation is passed to the IDoc.
    4.2.     S&D Sales Configurations
    4.2.1.     Maintain Item categories
    IMG  S&D  Sales  Sales document  Sales doc item  Define item categories
    Add LDN for standard item:
              Item type = B
              Relev for billing = B
              Tick following:     Bus data item
                                  Sched line allowed
                                  Credit active
                                  Pricing
              Screen seq. grp = N
    4.2.2.     Assign Item categories
    IMG  S&D  Sales  Sales document  Sales doc item  Assign item categories
    Add/Update the following entries:
         1     2     3
    Sales doc type     OR     OR     OR
    Item category group     NORM     DIEN     LEIS
    Item category     LDN     TAD
    LDN     LDN
    4.2.3.     Assign Schedule line categories
    IMG  S&D  Sales  Sales document  Schedule lines  Assign Schedule line categories
    Add Item category LDN to table (with no other parameters).
    4.3.     S&D Pricing Configurations
    4.3.1.     EDI pricing condition types
    IMG  S&D  Basic functions  Pricing  Pricing control  Define condition types  Maintain condition types
    Maintain the following condition types:
         EDI 1 - Calculate type =C for Quantity
         EDI 2 - Calculate type = B for Fixed amount
    4.3.2.     SD Pricing procedures (V/08)
    IMG  S&D  Basic functions  Pricing  Pricing control  Define & Assign pricing procedures
    Maintain pricing procedure for ZVAA01 (Standard). 
    Select control and add EDI1 and EDI2  as steps 1 and 5 respectively with no other parameters.
    5.     INVOICE IMG CONFIGURATION
    No additional IMG configuration (not partner specific) was needed for Inbound Invoice processing.
    Thanks,
    Swamy H P

  • Configured source directory .... does not exist was suppressed

    Hi,
    Below log is from PI 7.1 EHP1 system. I have tried to execute simple use cases from SDN but got below exception. The folder actually is there and there is not typing error. What could be the problem and any solution?
    Kind regards,
    Altug
    #2.0 #2010 05 11 01:57:10:002#+0300#Error#com.sap.aii.adapter.file.File2XI#
    #BC-XI-CON-AFW#com.sap.aii.af.lib#000C293D9117124200000000000007B0#9722350000001755##com.sap.aii.adapter.file.File2XI.getFileList(File2XIConfiguration.FileSource[])#J2EE_GUEST#0##488CE8105C4F11DF9D42000C293D9117#488ce8105c4f11df9d42000c293d9117#488ce8105c4f11df9d42000c293d9117#0#XI File2XI[XiPatternChannel_FileSender/PI7_FileSystem_XIPattern1/]_4767#Plain##
    Channel XiPatternChannel_FileSender: Directory C:
    work
    XIPattern1 does not exist#
    #2.0 #2010 05 11 01:57:10:002#+0300#Error#com.sap.aii.af.service.administration.impl.AlertingStatusListener#
    #BC-XI-CON-AFW#com.sap.aii.af.lib#000C293D9117124300000000000007B0#9722350000001755##com.sap.aii.af.service.administration.impl.AlertingStatusListener.run()#J2EE_GUEST#0##488CE8105C4F11DF9D42000C293D9117#488ce8105c4f11df9d42000c293d9117#488ce8105c4f11df9d42000c293d9117#0#XI AF AAM AlertingStatusListener$AsyncAlerter@67c2a0d6_4768#Java##
    Unable to raise alert for fatal process status (adapter :, channel ): com.sap.aii.af.service.alerting.AlertingException: An alert with suppress information:  Error Code:  Error Category:  Error text: Configured source directory 'C:
    work
    XIPattern1' does not exist was suppressed!Host:w2k3x64_PI7_00|AdapterType:File|Sender::PI7_FileSystem_XIPattern1|Receiver::|Interface:XiPatternInterface1:http://sap.com/xi/XI/System/Patterns|MsgID:null#3#http://sap.com/xi/XI/System#File#7be7f5b9e06c30cc97f90f55a21e150e#
    #2.0 #2010 05 11 01:57:20:002#+0300#Error#com.sap.aii.adapter.file.File2XI#
    #BC-XI-CON-AFW#com.sap.aii.af.lib#000C293D9117124400000000000007B0#9722350000001755##com.sap.aii.adapter.file.File2XI.getFileList(File2XIConfiguration.FileSource[])#J2EE_GUEST#0##488CE8105C4F11DF9D42000C293D9117#488ce8105c4f11df9d42000c293d9117#488ce8105c4f11df9d42000c293d9117#0#XI File2XI[XiPatternChannel_FileSender/PI7_FileSystem_XIPattern1/]_4769#Plain##
    Channel XiPatternChannel_FileSender: Directory C:
    work
    XIPattern1 does not exist#
    #2.0 #2010 05 11 01:57:20:017#+0300#Error#com.sap.aii.af.service.administration.impl.AlertingStatusListener#
    #BC-XI-CON-AFW#com.sap.aii.af.lib#000C293D9117124500000000000007B0#9722350000001755##com.sap.aii.af.service.administration.impl.AlertingStatusListener.run()#J2EE_GUEST#0##488CE8105C4F11DF9D42000C293D9117#488ce8105c4f11df9d42000c293d9117#488ce8105c4f11df9d42000c293d9117#0#XI AF AAM AlertingStatusListener$AsyncAlerter@1cfe7a5d_4770#Java##
    Unable to raise alert for fatal process status (adapter :, channel ): com.sap.aii.af.service.alerting.AlertingException: An alert with suppress information:  Error Code:  Error Category:  Error text: Configured source directory 'C:
    work
    XIPattern1' does not exist was suppressed!Host:w2k3x64_PI7_00|AdapterType:File|Sender::PI7_FileSystem_XIPattern1|Receiver::|Interface:XiPatternInterface1:http://sap.com/xi/XI/System/Patterns|MsgID:null#3#http://sap.com/xi/XI/System#File#7be7f5b9e06c30cc97f90f55a21e150e#
    #2.0 #2010 05 11 01:57:30:002#+0300#Error#com.sap.aii.adapter.file.File2XI#
    #BC-XI-CON-AFW#com.sap.aii.af.lib#000C293D9117124600000000000007B0#9722350000001755##com.sap.aii.adapter.file.File2XI.getFileList(File2XIConfiguration.FileSource[])#J2EE_GUEST#0##488CE8105C4F11DF9D42000C293D9117#488ce8105c4f11df9d42000c293d9117#488ce8105c4f11df9d42000c293d9117#0#XI File2XI[XiPatternChannel_FileSender/PI7_FileSystem_XIPattern1/]_4771#Plain##
    Channel XiPatternChannel_FileSender: Directory C:
    work
    XIPattern1 does not exist#
    #2.0 #2010 05 11 01:57:30:017#+0300#Error#com.sap.aii.af.service.administration.impl.AlertingStatusListener#
    #BC-XI-CON-AFW#com.sap.aii.af.lib#000C293D9117124700000000000007B0#9722350000001755##com.sap.aii.af.service.administration.impl.AlertingStatusListener.run()#J2EE_GUEST#0##488CE8105C4F11DF9D42000C293D9117#488ce8105c4f11df9d42000c293d9117#488ce8105c4f11df9d42000c293d9117#0#XI AF AAM AlertingStatusListener$AsyncAlerter@d023a80_4772#Java##
    Unable to raise alert for fatal process status (adapter :, channel ): com.sap.aii.af.service.alerting.AlertingException: An alert with suppress information:  Error Code:  Error Category:  Error text: Configured source directory 'C:
    work
    XIPattern1' does not exist was suppressed!Host:w2k3x64_PI7_00|AdapterType:File|Sender::PI7_FileSystem_XIPattern1|Receiver::|Interface:XiPatternInterface1:http://sap.com/xi/XI/System/Patterns|MsgID:null#3#http://sap.com/xi/XI/System#File#7be7f5b9e06c30cc97f90f55a21e150e#
    #2.0 #2010 05 11 01:57:40:002#+0300#Error#com.sap.aii.adapter.file.File2XI#
    #BC-XI-CON-AFW#com.sap.aii.af.lib#000C293D9117124800000000000007B0#9722350000001755##com.sap.aii.adapter.file.File2XI.getFileList(File2XIConfiguration.FileSource[])#J2EE_GUEST#0##488CE8105C4F11DF9D42000C293D9117#488ce8105c4f11df9d42000c293d9117#488ce8105c4f11df9d42000c293d9117#0#XI File2XI[XiPatternChannel_FileSender/PI7_FileSystem_XIPattern1/]_4773#Plain##
    Channel XiPatternChannel_FileSender: Directory C:
    work
    XIPattern1 does not exist#
    #2.0 #2010 05 11 01:57:40:002#+0300#Error#com.sap.aii.af.service.administration.impl.AlertingStatusListener#
    #BC-XI-CON-AFW#com.sap.aii.af.lib#000C293D9117124900000000000007B0#9722350000001755##com.sap.aii.af.service.administration.impl.AlertingStatusListener.run()#J2EE_GUEST#0##488CE8105C4F11DF9D42000C293D9117#488ce8105c4f11df9d42000c293d9117#488ce8105c4f11df9d42000c293d9117#0#XI AF AAM AlertingStatusListener$AsyncAlerter@76395415_4774#Java##
    Unable to raise alert for fatal process status (adapter :, channel ): com.sap.aii.af.service.alerting.AlertingException: An alert with suppress information:  Error Code:  Error Category:  Error text: Configured source directory 'C:
    work
    XIPattern1' does not exist was suppressed!Host:w2k3x64_PI7_00|AdapterType:File|Sender::PI7_FileSystem_XIPattern1|Receiver::|Interface:XiPatternInterface1:http://sap.com/xi/XI/System/Patterns|MsgID:null#3#http://sap.com/xi/XI/System#File#7be7f5b9e06c30cc97f90f55a21e150e#
    #2.0 #2010 05 11 01:57:50:002#+0300#Error#com.sap.aii.adapter.file.File2XI#
    #BC-XI-CON-AFW#com.sap.aii.af.lib#000C293D9117124A00000000000007B0#9722350000001755##com.sap.aii.adapter.file.File2XI.getFileList(File2XIConfiguration.FileSource[])#J2EE_GUEST#0##488CE8105C4F11DF9D42000C293D9117#488ce8105c4f11df9d42000c293d9117#488ce8105c4f11df9d42000c293d9117#0#XI File2XI[XiPatternChannel_FileSender/PI7_FileSystem_XIPattern1/]_4775#Plain##
    Channel XiPatternChannel_FileSender: Directory C:
    work
    XIPattern1 does not exist#
    #2.0 #2010 05 11 01:58:00:002#+0300#Error#com.sap.aii.adapter.file.File2XI#
    #BC-XI-CON-AFW#com.sap.aii.af.lib#000C293D9117124B00000000000007B0#9722350000001755##com.sap.aii.adapter.file.File2XI.getFileList(File2XIConfiguration.FileSource[])#J2EE_GUEST#0##488CE8105C4F11DF9D42000C293D9117#488ce8105c4f11df9d42000c293d9117#488ce8105c4f11df9d42000c293d9117#0#XI File2XI[XiPatternChannel_FileSender/PI7_FileSystem_XIPattern1/]_4777#Plain##
    Channel XiPatternChannel_FileSender: Directory C:
    work
    XIPattern1 does not exist#
    #2.0 #2010 05 11 01:58:00:002#+0300#Error#com.sap.aii.af.service.administration.impl.AlertingStatusListener#
    #BC-XI-CON-AFW#com.sap.aii.af.lib#000C293D9117124C00000000000007B0#9722350000001755##com.sap.aii.af.service.administration.impl.AlertingStatusListener.run()#J2EE_GUEST#0##488CE8105C4F11DF9D42000C293D9117#488ce8105c4f11df9d42000c293d9117#488ce8105c4f11df9d42000c293d9117#0#XI AF AAM AlertingStatusListener$AsyncAlerter@37d6d40_4778#Java##
    Unable to raise alert for fatal process status (adapter :, channel ): com.sap.aii.af.service.alerting.AlertingException: An alert with suppress information:  Error Code:  Error Category:  Error text: Configured source directory 'C:
    work
    XIPattern1' does not exist was suppressed!Host:w2k3x64_PI7_00|AdapterType:File|Sender::PI7_FileSystem_XIPattern1|Receiver::|Interface:XiPatternInterface1:http://sap.com/xi/XI/System/Patterns|MsgID:null#3#http://sap.com/xi/XI/System#File#7be7f5b9e06c30cc97f90f55a21e150e#

    Hi,
    Use this as a source directory mention the \ at last "C:
    work
    XIPattern1\"
    This doesn't help me. But later I give a permisson to the directory for everyone group. This time PI process worked and processed file.
    Thanks.
    Altug

Maybe you are looking for

  • Add ECC Custom Fields in CRM Web UI ERP Order item

    hi all, i have to Add ECC Custom Fields in CRM Web UI ERP Order item . I have : -  add the field on Web UI Screen. -  add the field on structure  TDS_item_COMV  and  TDS_item_COMC in ecc -  insert record for field on LORD_MAPPING table -  implemented

  • Pl/sql block updating orderId, itemID

    lol here i am again! This time its like this: i have a table (orderId, itemId, CustomerId, productId, quantity, start_date, end_date, oldRef) here are some of the values: 2477, 1, 201, 111, 1,19-MAR-93,14-APR-93 2477,2,201,112,1,19-MAR-93,14-APR-93 2

  • Iphone 4 will not connect to internet

    Hi i cant connect to internet through my phone network 3

  • Ts-L633a DVD drive not compatible with Windows 7 64bit upgrade

    Ts-L633a DVD drive on my Pavilion Dv7 1232nr is not compatible with Windows 7 64bit upgrade but will work fine if I downgrade back to Vista 64bit so what DVD drive is there other then the TS-L633a drive that I already have that is compatible with the

  • RAW Support for the New EOS 5D

    Please update the RAW plug-in to support the new Canon EOS 5D!