Skip to Content
author's profile photo Former Member
Former Member

Question on ALE Settings

Hi All....

What ALE settings needs to be created directly in Production Server I mean which are not able to trasnport to Test system/production system.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on May 30, 2008 at 11:20 AM

    Hi,

    First you should create and test in Development system only.

    once through the test then it should be move production system using Transport system

    Reward if found helpful,

    Regards,

    Boobalan Suburaj

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      hi,

      its been a while i have doen ALE settings. But if you want you can try on your own. When you do a particular settings which does not ask for a Transport request indicates that they have to be created in each and every system to which ALE communications takes place

      cheers

      VJ

      btw i recently read a SDN blog on a round about way to transport the distribution model by Aditya Palekar

      check this out

      /people/aditya.palekar/blog/2007/03/09/transporting-an-ale-distribution-model-into-qa-and-production-systems

      but generally in the industry it is created on the target system as well .

      always good to know stuff...cheers

      Edited by: Vijayendra Rao on May 30, 2008 7:43 AM

  • author's profile photo Former Member
    Former Member
    Posted on May 30, 2008 at 11:25 AM

    HI ,

    Direct Material Scenario with Planning in SAP APO

    Use

    Plan-driven procurement: If you do not wish to start the procurement process for direct materials manually from the procurement system, you can plan such requirements in an external planning system. You can use the SAP Advanced Planner and Optimizer (SAP APO) as a planning system. The following integration conditions, prerequisites, and restrictions then apply.

    Integration

    The scenario for procuring direct materials using SAP APO requires the integration of the following components:

    Component

    Function

    Activities

    SAP Enterprise Buyer

    Procurement system

    Purchasing, contract management

    SAP Advanced Planner and Optimizer (APO).

    Planning system

    Production planning and supply network planning

    SAP R/3 Backend System

    Executing system

    Goods receipt, invoice verification, material valuation and FI valuation

    SAP Business Information Warehouse (SAP BW)

    Reporting system

    Integrated reporting and supply of data for strategic vendor analysis

    SAP Enterprise Buyer can communicate with several executing backend systems but currently with only one SAP APO planning system.

    If SAP APO does not find a source of supply, the system transfers a requirement with data on plant, quantity, product, and delivery date to Enterprise Buyer.

    Enterprise Buyer automatically carries out sourcing for the requirements that have been transferred from SAP APO:

    · Using a sourcing control, Enterprise Buyer generates purchase orders depending on the number of sources of supply that have been determined.

    · Sourcing in Enterprise Buyer also processes requirements for which no source of supply has been found by the planning system. SAP APO only transfers such purchase requisitions if they lie within the opening period of planning. As soon as Enterprise Buyer has created a purchase order for a requirement, it notifies the planning system. The requirement can then no longer be changed in SAP APO.

    Prerequisites

    System Requirements

    · SAP APO with Release 3.0A or higher plus the relevant Support Package.

    · R/3 Release 3.1I or higher with EBP Plug-In and SAP Notes 313051 (Enterprise Buyer u2013 Direct Material in Purchasing) and related Notes as well as Note (Enterprise Buyer - S101 Direct Materials Procurement).

    Transaction Type/Document Type for Direct Materials

    · In the Enterprise Buyer System:

    You have created a transaction type and an appropriate number range for direct material purchase orders and assigned the transaction type as the value for the attribute DP_PROC_TY of the responsible purchasing group. See the section Settings in the Structure Organization in Enterprise Buyer

    · In the executing system:

    You have created a document type with the same name as the transaction type and the same number range, but with external number assignment.

    Settings in the Structure Organization in Enterprise Buyer

    You have defined the following:

    · An entry channel for SAP APO

    For more information, see the Supplier Relationship Management Implementation Guide (IMG): SRM Server ® Cross-Application Basic Settings ® Organizational Management ® Change Organizational Plan (transaction: PPOMA_BBP).

    · A remote user for Enterprise Buyer

    The user is linked with the organizational unit for the entry channel.

    The user has to be an Enterprise Buyer user, that is, a user with a business partner and a central person. A standard R/3 user is not sufficient.

    · Organizational responsibility for the entry channel

    You have assigned to the purchasing group the object ID of an organizational unit for which the purchasing group has organizational responsibility.

    The organizational unit of the purchasing group might be PGR1, and that of the entry channel might be O50001234. For PGR1 you choose object ID O50001234 of the organizational unit for which this purchasing group has organizational responsibility.

    · Attribute DP_PROC_TY (transaction type: direct material) for the purchasing group

    For more information, see Attributes for the Enterprise Buyer Scenario.

    · Attribute Locations

    Under Extended Attributes for a source system, you enter either the Partner ID or the plant ID of a location. The purchaser can carry out a procurement or a third-party deal for these locations only.

    · Attribute CUR (local currency) in the entry channel

    Sample Settings for Direct Procurement

    Remote Connections and ALE Settings

    You have defined the following remote connections and ALE settings for the logical system:

    · From Enterprise Buyer to the executing system

    · From Enterprise Buyer to the planning system

    · From the planning system to Enterprise Buyer. (Here, the RFC user is the EBP user from the entry channel)

    · From the planning system to the executing system

    · From the executing system to the planning system

    Location

    You have replicated the locations from the executing system using the report BBP_LOCATIONS_GET_ALL. See also SAP Note 563180 (locations - replication of R/3 plants)

    Further Settings in the Enterprise Buyer System

    You have made the following settings in the Enterprise Buyer system:

    · Master data replication

    You have replicated material groups, material types as product categories, materials as products, and terms of payment and vendors to the Enterprise Buyer system. See Replication of Materials from R/3 Backend Systems. Here you have replicated the R/3 materials lexicographically.

    See the path in the IMG: SRM Server ® Master Data ® Products ® Define Output Format and Storage Form of Product IDs

    · You have entered the logical system for the planning system as the value for the parameter CRMAPOATP. You use transaction R3AC6 for this. See the path in the SAP menu: Middleware ® Settings ® Define Middleware Parameters

    · You have defined the executing system and the planning system as backend systems. Choose the APO system, Release 3.0A, as system type for connection to SAP APO.

    See the path in the IMG: SRM Server ® Technical Basic Settings ® Define Backend Systems

    Further Settings in the Executing R/3 System

    You have made the following settings in the executing R/3 system:

    · You have entered target systems for integration in transaction CFC1.

    · You have created an integration model in transaction CFM1 and distributed plants, materials, purchase orders, stock, and vendors.

    · The materials that can be ordered as direct material have to be kept in stock. A responsible purchasing group must also exist.

    · You have activated and started the integration model in transaction CFM2.

    · You have configured the standard purchasing organization in the enterprise structure (transaction OMKI) for the plant.

    Further Settings in the APO Planning System

    You have made the following settings in the APO planning system:

    · You have defined a business system group in transaction /SAPAPO/C1.

    · You have assigned the logical executing system and the logical Enterprise Buyer system in transaction /SAPAPO/C2 to a business system group.

    · You have entered distribution definitions. These are used to define which plant-side requirements are transferred to which system.

    Menu path in the Implementation Guide (IMG): SAP Advanced Planner and Optimizer (APO) ® Basis Settings ® Integration ® Publication ® Maintain Distribution Definition

    · You can overwrite the recipient determinations contained in the distribution definitions:

    You can differentiate the target systems for external procurement orders (purchase requisitions and scheduling agreement releases) according to criteria with the user exits EXIT_/SAPAPO/SAPLCIF_G_EP_002 and EXIT_/SAPAPO/SAPLCIF_PUB_002 of enhancement APOCFPUB (from Release APO 3.0A). You can define more detailed rules for the recipient determination than just type/location/target system. See SAP Note 364118.

    For more information, see the documentation on APO Integration Scenarios.

    Settings for Reporting

    You have connected the SAP Business Information Warehouse (SAP BW) with your Enterprise Buyer System and the executing system. There are no special requirements for the procurement of direct materials. Both products and materials must be known in the BW reporting system to facilitate consolidation of the data.

    Business Add-Ins

    The following BAdIs are available in the Enterprise Buyer System:

    · Determine the executing system (BBP_DETERMINE_LOGSYS)

    With this BAdI, you can determine the executing system to which the direct material items are to be transferred. In the standard system, they are transferred to the system from which the product was replicated.

    See the path in the IMG: SRM Server ® Business Add-Ins for Enterprise Buyer (BAdIs) ® Shopping Carts and Requirement Items ® Determine Backend System/Company Code

    · Check items for APO relevance (CRM_APO_CHECK_REL)

    With this BAdI, you can control which items are transferred to the planning system, SAP APO. In the standard system, all items that contain a product and a plant (location) are transferred to the planning system.

    See the path in the IMG: SRM Server ® Business Add-Ins for Enterprise Buyer (BAdIs) ® Direct Material and Plan-Driven Procurement ® Check Items for APO Relevance

    · Control direct material procurement (BBP_DP_PROD_CHK_BADI)

    You can use this BAdI to control whether a product can be ordered as a direct material. In doing so, you overwrite the standard processing. A material is ordered as a direct material if the material has been replicated from the backend.

    See the path in the IMG: SRM Server ® Business Add-Ins for Enterprise Buyer (BAdIs) ® Direct Material and Plan-Driven Procurement ® Control Direct Material Procurement

    · Send shipping notification to planning system (BBP_XML_DET_SYSTEM)

    You can use this BAdI to control whether an inbound XML document is also sent to the planning system. In doing so, you overwrite standard processing. Normally, an inbound XML document is only sent to the backend system. You can use this to forward shipping notifications, for example.

    See the path in the IMG: SRM Server ® Business Add-Ins for Enterprise Buyer (BAdIs) ® Direct Material and Plan-Driven Procurement ® Send XML Document to Planning System

    Restrictions

    The scenarios for procurement of direct materials are subject to the following restrictions:

    · Shipping notifications that have been created in the R/3 backend system are not available in the Enterprise Buyer delivery information. You can also use shipping notifications that are sent directly to Enterprise Buyer for your materials planning and have them forwarded to the backend system too.

    · APO liveCache cannot be supplied with data from the Enterprise Buyer system at system start. If an initial supply is required, it has to come from the executing R/3 system.

    · The scenario does not support special forms of procurement (such as subcontracting or third party deals, for example).

    thanks

    karthik

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.