Pricing step by step procedure

Dear Experts,
pls send me the pricing notes ( step by step procedures) at my mail id
[email protected]
always reward point ...
Thanks b4 hand
Vaibhav

Hi Vaibhav,
Following are the steps you need to follow for pricing.
Reward if this helps you...
PRICING (PG)
This concept is based on condition technique.
It’s the combination of:
1)     Condition Tables
2)     Access Sequence
3)     Condition Types
4)     Pricing Procedure
1. Condition Tables: - Condition table contain the key fields for maintaining condition records.  I.e. in other words condition records are stored in condition table.
Note: - A condition type can have multiple condition tables.
Note: - A condition table can be used for multiple condition types.
Defining condition tables: -
SPRO
Sales and Distribution
Basic functions
Pricing
Pricing control
Define condition tables [V/03]
Create condition tables
Enter a table number beyond 600
From the field catalogue, which is there on the right side of the screen select the required key fields.
To get the valid on / valid to fields while maintaining the condition records we need to check the field “with validity period”.
Go to icon Technical View
The fields which are marked, as footer field appears at the footer level at the condition records and the remaining fields appears at the key level.
Select the Icon Generate for generating the condition table.
To save the condition table, select the button Local object.
2.     Access Sequence: - Access sequence is a search strategy with the help of which the system gets the valid condition records.  It contains the required condition tables in the required order.
Note: - If required an access sequence can be used or assigned to multiple
Condition types.
Note: - The order in which the condition table are placed in access sequence
is important generally it is most specific to most generic
Defining Access Sequence: -
SPRO
Sales and distribution
Basic functions
Pricing
Pricing control
Define access sequences
Maintain access sequences
Go to new entries and define the access sequence.
Select the defined access sequence and go to accesses.
Go to new entries and place the condition tables in the required order
While placing the condition tables check the field “exclusive”.  By doing so if the system finds a valid condition record in the first condition table it will not go to the next condition table
Select the condition table and go to fields the system gives the warning message “the field assignment has not yet been made” say enter till we get the fields.
Repeat the same step for all the condition tables and save it.
Note: - After defining the access sequence assign it to the corresponding condition type.
3. Condition Types: -
Defining condition types: -
SPRO
Sales and Distribution
Basic functions
Pricing
Pricing control
Define condition types.
Maintain condition types.
Functionality of a condition type: -
Access Sequence: - In this field specify the corresponding access sequence for the condition type.
Condition class: - It is the preliminary structuring of condition types.
Ex: - Surcharges or discounts and price
Plus/Minus: - If we specify negative here a condition type becomes discount and if we specify positive it becomes surcharge.
Calculation type: - Determines how the system calculates price discounts and surcharges in a condition type.
For Ex: - the system can calculate a price as a fixed amount or as a percentage based on the quantity, weight, or volume.
Condition Category: - It’s a classification of conditions according to pre-defined categories.
Rounding Rule: - The rule that determines how the system rounds of condition values during pricing.
Manual Entries: - Indicator which controls the priority with in a condition type between a condition enter manually and a condition automatically determined by the system.
Amount / Percent: - If we check this field the amount / percentage of a condition type can be change during the document processing.
Quantity Relation: - Specifies whether the conversion factors for the units of measure in the condition type can be change during document processing.
Delete: - If we check this field the condition type can be deleted during the sales document processing.
Value: - If we check this field the condition value can be changed during the document processing.
Calculation type: - If we check this field the calculation type can be change during the document processing.
Item condition: - If we check this field for a condition types it becomes item condition, which has to be enter at the item level only.
Header condition: - If we check this field for a condition type it becomes header condition, which has to be entered at the header level only
Ex: - RB00 (Discount).
Note: - After entering the header condition type click on the button activate.
Note: - The condition amount of the header condition is copied as it is to all the line items in the document
Group condition: - If we check a header condition as a group condition the condition amount is distributed proportionately among all the line items in the sales document.
Valid from & valid to: - specifies the beginning and ending of the validity date that the system automatically proposes when we create condition records for the condition types.
Scale Basis: - Determines how the system interprets a pricing scale in a condition, for Ex: - the scale can be based on quantity weight and volume.
Check value: - Indicates whether the sale rates must be entered in ascending or descending order.
Note: - Header condition won’t be having access sequence.
4. Pricing Procedure: - Pricing procedure contains all the required condition types in the required order.
Defining Pricing Procedure: -
SPRO
Sales and Distribution
Basic functions
Pricing
Pricing control
Define and assign pricing procedures.
Maintain pricing procedures
Go to new entries and define the pricing procedure.
Select the defined pricing procedure and go to control data
Go to new entries and place the required condition type in a specified order.
Step: - Specifies the number that determines the sequence of a condition type with in a procedure.
Counter: - Specifies the sequence number of a condition type with in a step in the procedure.
Condition type: - Specify the condition type.
From & To: - If you specify the reference steps in these fields, the condition values of the two steps specified and the condition values of the steps in between are totaled.
Manual: - If we check this field the condition type is only included in determination either if they are entered manually or if they are transferred from an external process such as costing.
Mandatory: - Indicates whether a condition type is mandatory when the system carries out pricing using the pricing procedure.
Statistical: - This indicator causes a condition type to be set in the document statistically only.
Print ID: - Controls the issue of condition lines when printing the documents such as order conformations or invoices. [X]
Sub Total: - Controls whether and in which fields the condition amounts or subtotals are stored.
Requirement: - For the condition type to be executed in the sales document the requirement specified here must be satisfied. [2]
Alternative calculation type: - Specifies the alternative formula to the calculation type in the standard system that determines a condition.
Alternative condition base value: - Specifies the formula for determining the condition basis as an alternative to the standard.
Account key: - This field along with few other fields enables the system to post the sales values to different General Ledger Accounts.
Ex: -
ERL          Sales Revenues
ERS          Sales Deductions
ERF          Freight Revenue
Accruals: - This is exclusively for rebate condition types. [B001 & B002]
Key, which identifies various types of General Ledger accounts for accruals posting.
Note: - to maintain the requirements and routines use the transaction code
[VOFM]
Pricing Procedure Determination: -
SPRO
Sales and Distribution
Basic Functions
Pricing
Pricing control
Define and Assign Pricing Procedures.
Define Pricing procedure determination [OVKK]
We have to assign the pricing procedure to the combination of Sales Organisation, Distribution Channel, Division, Document Pricing Procedure and customer pricing procedure.
Sales Organisations     Distribution Channels     Divisions     Doc. Pricing Procedure     Cus. Pricing Procedure
1000     10     00     A     01 & 02
2000     12     00     A     01 & 02

Similar Messages

  • Step-by step procedure for INBOUND IDOC (VENDOR CREATE / CHANGE)

    Hi ,
    Can any body provide me the step-by-step procedure for Inbound IDOCS.
    As i'm new to this i need the the clarification between Inbound & outbound idocs.
    How can we differentiate both?
    where to define outbound & where to define Inbound?
    ( If possible Please explain me the procedure for  Vendor Create through INBOUND IDOCS )
    Thanks in advance..

    Hi,
    Ale Technology is SAPu2019s technology to support distributed yet integrated processes across several SAP systems.
    Outbound Process:
    ALE Outbound Process in SAP sends data to one or more SAP Systems. It involves four steps.
    1. Identify the need of IDoc: This step starts upon creating a application document, can relate to a change to a master data object.
    2. Generate the Master IDoc: The document or master data to be sent is read from the database and formatted into an IDoc format. This IDoc is called as a Master IDoc.
    3. Generate the Communication IDoc: The ALE Service layer generates a separate IDoc from the Master IDoc for each recipient who is interested in the data. Separate IDocs are generated because each recipient might demand a different version or a subset of the Master IDoc. These recipient-specific IDocs are called Communication IDocs and are stored in the database.
    4. Deliver the Communication IDoc: The IDoc is delivered to the recipients using an asynchronous communication method. This allows the sending system to continue its processing without having to wait for the destination system to receiver or process the IDoc.
    Inbound Process:
    The inbound process receives an IDoc and creates a document in the system.
    1. Store the IDoc in the database: The IDoc is received from the sending system and stored in the database. Then the IDoc goes through a basic integrity check and syntax check.
    2. Invoke the Posting Module: The control information in the IDoc and configuration tables are read to determine the posting program. The IDoc is then transferred to its posting program.
    3. Create the Document: The posting program reads the IDoc data and then creates a document in the system. The results are logged in the IDoc.
    Over view of IDocs:
    IDoc is a container that is used to exchange data between any two processes. The document represented in an IDoc is independent of the complex structure SAP uses to store application data. This type of flexibility enables SAP to rearrange its internal structure without affecting the existing interface.
    IDoc interface represents an IDoc Type or IDoc data. IDoc Type represents IDocu2019s definition and IDoc Data is an instance of the IDoc Type.
    IDoc Types:
    IDoc type structure can consist of several segments, and each segment can consist of several data fields. The IDoc structure defines the syntax of the data by specifying a list of permitted segments and arrangement of the segments. Segments define a set of fields and their format.
    An IDoc is an instance of an IDoc Type and consists of three types of records.
    i. One Control record: each IDoc has only one control record. The control record contains all the control information about an IDoc, including the IDoc number, the sender and recipient information, and information such as the message type it represents and IDoc type. The control record structure is same for all IDocs.
    ii. One or Many Data records: An IDoc can have multiple data records, as defined by the IDoc structure. Segments translate into data records, which store application data, such as purchase order header information and purchase order detail lines.
    iii. One or Many Status records: An IDoc can have multiple status records. Status record helps to determine whether an IDoc has any error.
    Message in IDoc Type:
    A Message represents a specific type of document transmitted between two partners.
    Outbound Process in IDocs:
    Outbound process used the following components to generate an IDoc. A customer model, and IDoc structure, selection programs, filter objects, conversion rules, a port definition, an RFC destination, a partner profile, service programs, and configuration tables.
    The Customer Model:
    A customer model is used to model a distribution scenario. In a customer model, you identify the systems involved in a distribution scenario and the message exchanged between the systems.
    Message control:
    Message control is a cross application technology used in pricing, account determination, material determination, and output determination. The output determination technique of Message control triggers the ALE for a business document. Message control separates the logic of generating IDocs from the application logic.
    Change Pointers:
    The change pointers technique is based on the change document technique, which tracks changes made to key documents in SAP, such as the material master, customer master and sales order.
    Changes made to a document are recorded in the change document header table CDHDR, and additional change pointers are written in the BDCP table for the changes relevant to ALE.
    IDoc Structure:
    A message is defined for data that is exchanged between two systems. The message type is based on one or more IDoc structures.
    Selection Program:
    Is typically implemented as function modules, are designed to extract application data and create a master IDoc. A selection program exists for each message type. A selection programu2019s design depends on the triggering mechanism used in the process.
    Filter Objects;
    Filter Objects remove unwanted data for each recipient of the data basing on the recipients requirement.
    Port Definition:
    A port is used in an outbound process to define the medium in which documents are transferred to the destination system. ALE used a Transactional RFC port, which transfers data in memory buffers.
    RFC Destination:
    The RFC destination is a logical name used to define the characteristics of a communication link to a remote system on which a function needs to be executed.
    Partner Profile:
    A partner profile specifies the components used in an outbound process(logical name of the remote SAP system, IDoc Type, message type, TRFC port), an IDocu2019s packet size, the mode in which the process sends an IDoc (batch versus immediate), and the person to be notified in case of error.
    Service Programs and Configuration Tables:
    The outbound process, being asynchronous, is essentially a sequence of several processes that work together. SAP provides service programs and configuration tables to link these programs and provide customizing options for an outbound process.
    Process flow for Distributing Transactional Data:
    Transactional data is distributed using two techniques: with Message control and without message control.
    Process flow for Distributing Master Data:
    Master data between SAP systems is distributed using two techniques: Stand alone Programs and Change Pointers.
    Triggering the Outbound Process via Stand-Alone Programs:
    Stand-Alone programs are started explicitly by a user to transmit data from one SAP system to another. Standard Programs for several master data objects exist in SAP. Ex. The material master data can be transferred using the RBDSEMAT program or transaction BD10.
    The stand-alone programs provide a selection screen to specify the objects to be transferred and the receiving system. After the stand-alone program is executed, it calls the IDoc selection program with the specified parameters.
    Triggering the Outbound Process via Change Pointers:
    The change pointer technique is used to initiate the outbound process automatically when master data is created or changed.
    A standard program, RBDMIDOC, is scheduled to run on a periodic basis to evaluate the change pointers for a message type and start the ALE process for distributing the master data to the appropriate destination. The RBDMIDOC program reads the table TBDME to determine the IDoc selection program for a message type.
    Processing in the Application Layer:
    The customer distribution model is consulted to make sure that a receiver has been defined for the message to be transmitted. If not, processing ends. If at least one receiver exists, the IDoc selection program reads the master data object from the database and creates a master IDoc from it. The master IDoc is stored in memory. The program then calls the ALE service layer by using the function module MASTER_IDOC_DISTRIBUTE, passing the master IDoc and the receiver information.
    Processing in the ALE Interface Layer:
    Processing in the ALE Layer consists of the following steps:
    u2022 Receiver Determination: The determination of the receiver is done through Customer Distribution Model.
    u2022 IDoc Filtering: if an IDoc filter is specified in the distribution model for a receiver, values in the filter are compared against the values in the IDoc data records. If a data record does not meet the filter criteria, it is dropped.
    u2022 Segment Filtering: For each sender and receiver combination, a set of segments that are not required can be filtered out.
    u2022 Field conversion: Field values in data records are converted by using the conversion rules specified for the segment.
    u2022 Version change for segments: Segments are version-controlled. A new version of a segment always contains fields from the preceding version and fields added for the new version. Release in IDoc type field of the partner profile to determine the version of the segment to be generated.
    u2022 Version change for IDocs: IDocs are also version controlled. The version is determined from the Basic Type field of the partner profile.
    u2022 Communication IDocs generated: The final IDoc generated for a receiver after all the conversions and filtering operations is the communication IDoc. One master IDoc can have multiple communication IDocs depending on the number of receivers identified and the filter operations performed. IDoc gets the status record with a status code of 01 (IDoc Created).
    u2022 Syntax check performed: IDoc goes through a syntax check and data integrity validation. If errors found the IDoc get the status of 26 (error during syntax check of IDoc u2013 Outbound). If no errors found the IDoc gets the status 30 (IDoc ready for dispatch u2013 ALE Service).
    u2022 IDoc dispatched to the communication Layer: In the ALE process, IDocs are dispatched using the asynchronous RFC method, which means that the sending system does not await for data to be received or processed on the destination system. After IDocs have been transferred to the communication layer, they get a status code 01 (Data Passed to Port OK).
    Processing in the Communication Layer:
    To dispatch an IDoc to a destination system, the system reads the port definition specified in the partner profile to determine the destination system, which is then used to read the RFC destination. The RFC destination contains communication settings to log o to the remote SAP system. The sending system calls the INBOUND_IDOC_PROCESS function module asynchronously on the destination system and passes the IDoc data via the memory buffers.
    Inbound Process in IDocs:
    An inbound process used IDoc structure, posting programs, filter objects, conversion rules, a partner profile, service programs, and configuration tables to post an application document from an IDoc.
    Posting Program:
    Posting programs, which are implemented as function modules, read data from an IDoc and create an application document from it. A posting program exists for each message. Each posting program is assigned a process code. A process code can point to a function module or a work flow. In the standard program process codes always point to a function module.
    Ex. The posting program for message type MATMAS is IDOC_INPUT_MATMAS which has a process code MATM.
    Workflow:
    A workflow represents a sequence of customized steps to be carried out for a process. The workflow management system is used to model the sequence, identify information required to carry out the steps and identify the person responsible for the dialog steps.
    Partner Profile;
    A partner profile specifies the components used in an inbound process (partner number, message type, and process code), the mode in which IDocs are processed (batch versus immediate), and the person to be notified in case of errors.
    Process flow for the Inbound process via a Function Module:
    In this process, IDocs are received from another system and passed to the posting function module directly.
    1. Processing in the communication Layer:
    The IDOC_INBOUND_ASYCHRONOUS program, triggered as a result of an RFC from the sending system, acts as the entry point for all inbound ALE processes. The IDoc to be processed is passed as an input parameter. Control is transferred to the ALE/EDI layer.
    2. Processing in the ALE/EDI Interface Layer:
    u2022 Basic integrity check: A basic integrity check is performed on the control record.
    u2022 Segment Filtering and conversion: Filtering out unwanted segments and carry out any required conversion of field values.
    u2022 Creation of Application IDoc: The application IDoc is created and stored in the database and a syntax check is performed. If there are errors it gets status code of 60 (Error during Syntax check of IDoc u2013 Inbound). At this point a tangible IDoc, which can be monitored via one of the monitoring transactions, is created and the IDoc gets status code 50 (IDoc Added).
    u2022 IDoc Marked ready for Dispatch: IDoc gets the status code 64 (IDoc ready to be passed to application).
    u2022 IDoc is passed to the posting program: The partner profile table is read. If the value of the Processing field is set to Process Immediately, the IDoc is passed to the posting program immediately using the program RBDAPP01.
    3. Processing in the Posting Module:
    The process code in the partner profile points to a posting module for the specific message in the IDoc. The posting program implemented as a function module either calls a standard SAP transaction by using the Call Transaction command for posting the document or invokes a direct input function module.
    The results of execution are passed back via the function moduleu2019s output parameters. If the posting is successful IDoc gets the status code 53 (Application Document Posted) or it gets status code 51 (Error: Application Document Not Posted).

  • Step-by-step procedure to enter condition record?

    Hi ,
    Could someone please explain the step-by-step procedure to enter condtion record for pricing when creating a sales order?

    Hello,
    Please refer to the SAP online help; this is not a subject for the Abap forum.
    Regards,
    John.

  • Step by Step document on Guided Procedures for Benefits.......Help Needed..

    Hello Gurus,
    We are in process of implementing Benefits and for which we are using Guided Procedures, want to have understanding of the process can you please provide the step by step documentation and an example process that will be of great help.
    Appreciate your help.
    Thanks in advance for your time.
    Kind Regards,
    Pramod

    Hi Pramod,
    Please have a look at the below links. You will probably get some help.
    First of all, see the following thread, see the answer by shen peng in the end, explained CAF in very simple terms:
    https://www.sdn.sap.com/irj/sdn/thread?threadID=470956&tstart=0
    Now have a look at the following links for understanding about CAF, :
    <a href="https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/4277f37b-0601-0010-0597-89e792177e2b">Creating Composite Applications with SAP CAF</a>
    <a href="https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/84df3e36-0301-0010-be9d-b99aad8c81e6">Composite Application Framework in SAP NetWeaver</a>
    <a href="https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1122">CAF training material online</a>
    <a href="https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1231">Additional CAF Training material online</a>
    See the following links for understanding CAF GP in detail:
    <a href="https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/0b1c2eda-0c01-0010-b597-b107502cdc71">CAF Guided Procedures Overview</a>
    <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/39/198141f906040de10000000a1550b0/frameset.htm">CAF Guided Procedures</a>
    <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/c7/984942da51690de10000000a155106/frameset.htm">Concepts of the Guided Procedures Framework</a>
    Lastly, see the following links for CAF GP Wiki Home Page and CAF Tutorial Center:
    <a href="https://wiki.sdn.sap.com/wiki/display/BPX/Guided+Procedures">CAF Guided Procedures Wiki Home Page</a>
    <a href="https://www.sdn.sap.com/irj/sdn/nw-composition?rid=/webcontent/uuid/d8dbd703-0801-0010-c9bf-c04bc52f562f">Composite Application Framework Tutorial Center</a>
    You can also have a look at the following thread, you can drill down into many more links:
    https://www.sdn.sap.com/irj/sdn/thread?threadID=405517&tstart=0
    https://www.sdn.sap.com/irj/sdn/thread?threadID=314804&tstart=50
    Bye
    Ankur

  • Step by Step procedure for Integration of B0 with BI 7.0, Portal

    Hi,
    My key concerns include integration with SAP Portal, which I did not find in instalaltion guide.
    Please advice on step by by Procedure for BO with BI 7.0 starting with the right version of BO to be installed.
    1. Which version compatible with BI 7.0 SP 12, LATER TO BE UPGRADED TO sp 16
    2. Source of data will be BI and reports will be using BO.
    3. What are components to be installed
    4. Prerequisites for Integration with BI AND SAP Portal.
    5.Steps for Integration with BI 7.0
    6. Steps for Integration with SAP Portal- Where to get the sample iviews. What to do for connction between Portal and BO - this i didnt find in installation guide
    Thanks,
    Harish

    HI,
    here the items:
    SAP Side:
    - all machines have to be in the same domain
    - BI has to trust the portal
    - BI has to accept SSO tickets
    - EP has to generate SSO tickets
    BusinessObjects:
    - SAP Authentication has to be configured
    - BI system should be configured has default system in the options of the SAP authentication
    - authentication.default parameter in the web.xml for InfoView has to be set to secSAPR3
    - BusinessObjects has to be in the same domain
    EP side:
    - in the system landscape configure the Crystal Enterprise Server Properties for your BI system
    - import the portal iview template that is part of the SAP Integration Kit
    - create a new iView
    Ingo

  • I just replaced my hard drive and am trying to install the Snow Leppard OS on my Mac mini using the DVD's that came with the unit. Is there a step by step procedure that will guide me through this process?

    I just replaced my hard drive due to failure in my Mac mini. I am trying to load the Snow Leppard OS from the DVD's that came with the unit. Is there a step-by-step procedure somewhere that would help me? This is my first problem with my first Mac. I thought getting to the hard drive and changing it would be the hard part but I made it through that with little trouble. My lack of software experience on the Mac is really slowing me down. I believe I'm not making the right choices in the Disk Utility program.Any help would be greatly appreciated. Thank you.

    Prep the new drive:
    Drive Preparation
    1.  Boot from your OS X Installer Disc. After the installer loads select your language and click on the Continue button.  When the menu bar appears select Disk Utility from the Utilities menu.
    2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area.  If it does not say "Verified" then the drive is failing or has failed and will need replacing.  SMART info will not be reported  on external drives. Otherwise, click on the Partition tab in the DU main window.
    3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, set the partition scheme to GUID then click on the OK button. Click on the Partition button and wait until the process has completed.
    4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
    5. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, check the button for Zero Data and click on OK to return to the Erase window.
    6. Click on the Erase button. The format process can take up to several hours depending upon the drive size.
    Upon completion quit DU and return to the installer. Install OS X. When the installation has completed you can proceed to restore your data from your backups. If you have an existing backup from Time Machine or another hard drive then upon completing the Setup Assistant you will have an option to restore from another Mac, a TM backup, or another drive. Use the appropriate option.

  • Step by step procedure for Upgrade to ECC6.0

    Hi,
    I gained a lot from this forum . Can someone please mail me at
    [email protected]
    step by step procedure for upgrade .
    Will award full points for helpful documents..
    With regards,
    Mrinal

    SAP defined a roadmap for upgrade.
    1) Project Preparation
    Analyze the actual situation
    Define the objectives
    Create the project plan
    Carry out organizational preparation for example identify the project team
    2)Upgrade Blueprint
    The system and components affected
    The mapped business processes
    The requirements regarding business data
    3)Upgrade Realization -- In this phase the solution described in the design phase is implemented in a test environment. This creates a pilot system landscape, in which the processes and all their interfaces can be mapped individually and tested on the functional basis.
    4)Final Preparation for Cutover -- Testing, Training, Minimizing upgrade risks, Detailed upgrade planning
    5)Production Cutover and Support
    The production solution upgrade
    Startup of the solutions in the new release
    Post processing activities
    Solving typical problems during the initial operation phase.
    SAP expects at least 2 to 3 months for Upgrade and that again depends on project scope and complexity and various other factors.
    STEPS IN TECHNICAL UPGRADE
    •     Basis Team will do the prepare activities. (UNIX, BASIS, DBA).
    •     Developer need to run the Transaction SPDD which provides the details of SAP Standard Dictionary objects that have been modified by the client. Users need to take a decision to keep the changes or revert back to the SAP Standard Structure. More often decision is to keep the change. This is mandatory activity in upgrade and avoids data loses in new system.
    •     After completing SPDD transaction, we need to run SPAU Transaction to get the list of Standard SAP programs that have been modified.  This activity can be done in phases even after the upgrade. Generally this will be done in same go so that your testing results are consistent and have more confident in upgrade.
    •     Run SPUMG Transaction for Unicode Conversion in non-Unicode system. SPUM4 in 4.6c.
    •     Then we need to move Z/Y Objects.  Need to do Extended programming check, SQL trace, Unit testing, Integration testing, Final testing, Regression Testing, Acceptance Testing etc.,
    The main Category of Objects that needs to be Upgraded is –
    •     Includes
    •     Function Groups / Function Modules
    •     Programs / Reports
    •     OSS Notes
    •     SAP Repository Objects
    •     SAP Data Dictionary Objects
    •     Domains, Data Elements
    •     Tables, Structures and Views
    •     Module Pools, Sub Routine pools
    •     BDC Programs
    •     Print Programs
    •     SAP Scripts, Screens
    •     User Exits
    Also refer to the links -
    http://service.sap.com
    http://solutionbrowser.erp.sap.fmpmedia.com/
    http://help.sap.com/saphelp_nw2004s/helpdata/en/60/d6ba7bceda11d1953a0000e82de14a/content.htm
    http://www.id.unizh.ch/dl/sw/sap/upgrade/Master_Guide_Enh_Package_2005_1.pdf
    Hope this helps you.

  • Step By step procedures  for various scenarios Required ASAP!!!!!

    Hi All,
    Pls mail me the step by step procedure of the following scenaios.
    1.) File-XI-File Scenario.
    2.) Text file scenario.
    3.)File to Idoc
    4.)File XI- RFC.(R/3)
    5.) BPM scenarios.
    any stuff related pls mail to [email protected]
    Thanks in Advance.
    Sofia.

    Hi Sofia,
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
    /people/ravikumar.allampallam/blog/2005/06/24/convert-any-flat-file-to-any-idoc-java-mapping - Any flat file to any Idoc
    /people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy - ABAP Proxy to File
    /people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30 - File to JDBC
    /people/prateek.shah/blog/2005/06/14/file-to-r3-via-abap-proxy - File to ABAP Proxy
    /people/venkat.donela/blog/2005/03/02/introduction-to-simplefile-xi-filescenario-and-complete-walk-through-for-starterspart1 - File to File Part 1
    /people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2 - File to File Part 2
    /people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit - File to RFC
    https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1685 [original link is broken] [original link is broken] [original link is broken] [original link is broken] - File to Mail
    BPM Scenarios:-
    /people/krishna.moorthyp/blog/2005/06/09/walkthrough-with-bpm
    /people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
    Regards.
    Praveen

  • BI 7.0 Report Designer  Step by step procedure

    Hi,
    I have searched in Forum but no where i found BI 7.0 Report Designer  please can anyone provide me  Step by Step Procedure it will be great helpful to me .
    Thanks,
    Medha.

    hi Medha,
    Report Designer FAQ;
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/7254cb74-0901-0010-4fbf-9b7cb2459f1d
    how to document is;
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/709e2d84-0d53-2a10-928a-d9a565ec010c
    hope it help.
    Hanna

  • Step by step procedure in module pool..programming

    hi
         can any one give me the step by step procedure of module pool programming .. at present iam in mm module pool programming...urgent..
    regards
    veera

    Check the below link:
    http://sap.mis.cmich.edu/sap-abap/abap09/index.htm
    Simple program to create module pool.
    http://wiki.ittoolbox.com/index.php/FAQ:What_is_module_pool_program_in_abap%3F
    http://help.sap.com/saphelp_46c/helpdata/en/35/26b1aaafab52b9e10000009b38f974/content.htm
    http://sap.mis.cmich.edu/sap-abap/abap09/sld011.htm
    http://sap.mis.cmich.edu/sap-abap/abap09/index.htm
    You can also check the transaction <b>ABAPDOCU</b> which gives you lot of sample programs.
    Regards,
    Prakash,.

  • Step by Step procedure for ALE

    Dear Friends,
    Can anyone please post the step by step procedure of creating ALE with an example.
    Regards
    SN

    Hi,
    Follow the below steps outbound side for IDoc transfer.
    1. Create logical system (t-code BD54)
    2. Assign client to logical system (t-code SCC4)
    3. Create Ports (t-code WE21)
    4. Create Partner Profile (t-code WE20)
    5. Create Distribution model (t-code BD64)
    At the inbound side,
    1. Create logical system (t-code BD54)
    2. Assign client to logical system (t-code SCC4)
    3. Create Partner Profile (t-code WE20)
    4. At the outbound side, once you create the distribution model, select the model, and from the menu bar, select, Edit->Model view->distribute.... this will create the model view at the receiver.
    Now use the respective transactions to send the respective customer or vendor or....of ur need.
    ~ Bineah

  • Step by step procedure to connect SAP XI(Seerburger adapter) wi EDI partner

    hi,
    I need to know what kind of scenario we have go with seerburger adapter to connect with EDI partner?
    give some example scenarios and step by step procedure to connect SAP XI(Seerburger adapter) with  EDI partner?
    regards
    Ruban
    Message was edited by:
            ruban R

    hi,
    i found these weblogs,
    /people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
    /people/william.li/blog/2006/03/17/how-to-get-started-using-conversion-agent-from-itemfield
    /people/paul.medaille/blog/2005/11/17/more-on-the-sap-conversion-agent-by-itemfield
    other than any other weblog for this scenario for AS2 adapter for abap proxy to EDI partner to send purchase order ?

  • BAPI STEP BY STEP PROCEDURE

    hii abapers,
            i have no idea about how to implement a BAPI interface.... PLZ GUIDE me with the step by step procedure (with screen shots) of how to implement a BAPI..
    thanks.
    with regard
    K.Saravanakumar

    u can check these :
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2a1dd5d3-0801-0010-ed8d-bd797ed922cb
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/200dd1cc-589e-2910-98a9-bb2c48b78dfa
    Madhavi

  • Step by Step procedure to create an entire scenario Using CAF

    Dear All,
        I have a scenario to develop using Composite Application Framework.After creating the CAF i need to display the CAF on the portal. step by step procedure(if possible with screen shots) to create a CAF and how to find web services and then display this application on portal.
    Thanks

    Hi Yogi,
    In your sceanario if you are looking to build either Enity or Application service then create it and test that service from "Service Browser". Once your service is working as per your reqyurements then we have to options to bring it into the Portal:
    1. Generate Web Service for you Service (Entity or Application).
    2. Consume that Web Service in WebDynpro application using Model concepts.
    3. Deploy your WebDynpro Application into your portal Server.
    4. Create a WebDynpro iView for your application and assign it any where you want.
                                                         OR
    1. Generate WebDynpro model for your CAF application.
    2. Create a public part for you application webdynpro project of your CAF application.
    3. Create a new WebDynpro DC and use the Models generated for your CAF application.
    4. Deploy your WebDynpro Application into your portal Server.
    5. Create a WebDynpro iView for your application and assign it any where you want.
    If you can give your complete scenario then that would be more helpful for any one to provide best answer which is approapriate for you.
    Thanks,
    Uday.

  • Step-by-Step procedure to create an InfoPackage Group & a Scenario!!

    Hello BW Experts,
    IF we have 10 InfoPackages and if we need to create an InfoPackage Group for 7 of them, How do we do it??
    Plz provide a detailed Step-by-Step procedure for the same/ create an InfoPackage group!!
    Ur help is really appreciated!!
    Thanks & Regards,
    Sapster.

    Hello Stefan,
    Thanks for ur response...with ur detailed steps..really helpful.
    While sheduling at the last ..by clicking the context menu of our created IP Group.. I am not getting any screen to schedule the same..(I am getting amessage at the mottom saying its not possible to run it in the back ground for my client workstation or similar to this)
    Could u plz let me know.. what it looks like for these remaining steps
    "Right click on the InfoPackage Group that you just created -> Schedule -> Check that all InfoPackages are selected -> Schedule the job just as you normally do with a InfoPackage."... thansk again.. assigend points...

Maybe you are looking for

  • Datacopy from Dynamic Calc member

    Hi All, Within a dense dimension(Accounts) I want to copy data from dynamic calc member to a stored member. Below is the structure of my dimension. Member X (~, Stored) Member A (Dynamic calc, TBLast) ----Member A1 (Dynamic Calc) ----Member A2 (Dynam

  • Html email question

    I'd like to add a bit of text to my mail signature, something like this: Check out my istock portfolio So that it comes out like this: 'Check out my istock portfolio' - as a link. Is it possible? Thanks for reading, hope to hear from you Brgds Alex

  • Space-bar-is-not-working

    I-just-took-the-bottom-three-rows-off-my-dirty-keyboard,-washed-the-keys-in-soap y-water,-and-cleaned-the-blank-rows-where-the-keys-were,-using-a-cotton-swab-and -soapy-water.-I-rinsed-the-keys-off-and-replaced-them.-All-of-the-keys-work-beau tifully

  • Migration from MS access to sql server

    Hi, I need to move e-manager db from a MS Access to a SQL server. I succeeded in moving all tables, relations and views but I run into problems when executing the view lTestCases_Requirement . I get a sql execution error due to a data type conversion

  • I Cloud help please

    Good morning - I am trying to set up ICloud on my up to date MAC laptop and it does not offer me the Icloud under settings.  It has Mobile Me on the cloud icon and that will not let me in.  Help???.