copy controls in sap sd

SAP SD Copy Control functionality allows to define which information will be copied from the source document to the target document. SAP SD Copy Control is configured at both Header and Item levels. At the header level, you define which source document can be copied into which target document and at the item level you define copying requirements with regard to the item categories.

If the document flow between documents is missing, the system will not be able to copy information from one sales document to another one. Example of document flow is creation of a sales order with a reference to a quotation. In this case, the quotation is a source document and the sales order is the target document.

SAP SD Copy Control can be maintained for the following areas:

Sales Documents

• Sales to Sales Document: Inquiry to Quotation to Contract to Sales Order and Returns Order with reference to Sales Order
• Billing to Sales Document: Referring Billing Document to create Credit or Debit Memo Request(s)

Deliveries

• Sales to Delivery Document: Sales Order to Delivery Document

Billing Documents

• Sales to Billing Document: In case of Cash Sales or Services and Order Related Billing
• Billing to Billing Document: Cancelling Billing Document, Invoice List, Credit Memo List
• Delivery to Billing Document: In case of Delivery Related Billing

How to Configure SAP SD Copy Control?

To configure or maintain SAP SD Copy Control at the backend in the SAP system, you can either type SPRO in the transaction bar or navigate through SAP Easy Access menu to this path:

Tools > Customization > IMG > SPRO – Execute Project

Next, you should navigate to the following menu node in SPRO and start this activity:

SPRO > Sales & Distribution > Sales > Maintain Copy Control

In the pop-up window, let’s choose Sales to Sales Document. This activity can also be accessed directly using the transaction code VTAA.

SAP SD Copy Control – Maintenance > Sales Documents to Sales Documents

To view settings of SAP SD Copy Control at the header level for a particular sales document type, select the relevant line and double click on it or press  button in the toolbar.

SAP SD Copy Control – Maintenance > Sales Documents to Sales Documents > Header

Here you can see the header copy control where the target document is sales order type ZDEM and the source is quotation type QT. This means that the sales order type ZDEM can be created by referring to quotation type QT.

SAP SD Copy Control – Maintenance > Sales Documents to Sales Documents > Header > Copy

The Copy section of the configuration screen contains copying requirement which are routines (programs) provided in the standard SAP system. These routines can be customized for any special business scenario with the help of an ABAP developer.

The copying routines selected the left-side fields are related to business data transfer. For example, general header data, business data and partner data. These identifies a routine that checks whether certain requirements are met during the transfer of data from these fields to target document during copying.

On the right side, copying requirement allows to perform certain checks. The routine checks that certain requirements are met when one document is copied into another. For instance, if any of the line items is rejected in the source document, this document should not be copied into the target document.

Now, let’s have a look at SAP SD copy control at the item level. To do it, click on Item icon in the left sidebar. The SAP system will show you the list of tem categories maintained for target and source sales document types.

SAP SD Copy Control – Maintenance > Sales Documents to Sales Documents > Item > Select Item Category

Select the item category for which you want to maintain settings and double click on it or press  button on the toolbar.

SAP SD Copy Control – Maintenance > Sales Documents to Sales Documents > Item

Here at the item level you can see routines that will work during copying of items data. There are many standard routines provided by SAP but if there is any specific business requirement not covered by the standard routines, a customized routine can be developed with the help of an ABAP programmer.

Standard Routines for SAP SD Copy Control at Item Level

Similar to the settings for the header level of copy control, you can set a number of different routines for performing checks and transferring data during copy of one sales document to another. In addition to routines, there are also several indicators.

Copy schedule lines: this check shows whether the schedule lines from the source document are copied to the target document.

Update document flow: defines if the system will create new entries in the document flow when new target documents are created with a reference to the source document.

Do not copy batch: this checkbox enables you to control copying of batch number(s) from the source to the target document.

Pos./neg. quantity: this indicator defines whether during copying the quantity in the target document has a negative, positive or no effect at all on the quantity still to be completed in the source document.

Copy quantity: The quantity that is copied in the target document. The system can either determine it automatically or copy order quantity or copy target quantity.

Pricing type: This option defines whether the pricing to be re-calculated every time when the target document is created with a reference to the source document or if re-pricing should not run and it should be copied from the source document to the target document as it is. There are also additional rules which are provided in the standard system.

Transaction Codes for SAP SD Copy Control

When you work with configuring copy control it can be tiresome to navigate using SPRO menu. Luckily, there are direct transaction codes for starting the configuration of SAP SD copy control for different areas. For your reference, they are listed below.

Sales

• Sales Document to Sales Document: transaction VTAA
• Billing Document to Sales Document: transaction VTAF

Delivery

• Sales Document to Delivery Documents: transaction VTLA

Billing

• Sales Document to Billing Document: transaction VTFA
• Billing Document to Billing Document: transaction VTFF
• Delivery Document to Billing Document: transaction VTFL

sap sd interview questions for freshers

1) What is the organizational structure in sales and distribution?

The organizational structure in sales and distribution is

• Sales Organization
• Distribution Channel
• Division
• Sales Office
• Sales Group

2) Explain what is the difference between milestone and periodic billing?

• Periodic: Full amount in each bill till contract period
• Milestone: Partial amount in each bill till full amount is billed

3) Explain how shipping point is determined?

Shipping point is determined by,

Shipping Conditions + Loading Group + Delivery Plant = Shipping Point

4) Explain how you can assign distribution channel to Sales Organization?

To assign distribution to sales organization in SAP, you have to follow the path

SPRO (SAP Project Reference Object) >IMG >Enterprise structure >Assignment > Sales and Distribution > Assign distribution channel to sales organization

5) What is SAP SD? What are the primary functions of Sales and Distribution?

SAP SD handles all the processes of order to delivery. It executes the business processes used in selling, shipping and billing of product and services.

• Inquiries & Quotes
• Sales Orders
• Sales Return
• Consignment
• Contract & Scheduling Agreements
• Credit & Debit Memo requests
• Rush Orders & Cash Sales
• Back Orders

6) Mention what are the Sales Document types in SAP? What is the configuration step to define sales document type in SAP SD?

The Sales Document types available in SAP are

• Credit Memo Request
• Debit Memo Request
• Standard Order
• Returns, etc.

Configuration steps for SAP SD
IMG Menu Path: SPRO > IMG > Sales and Distribution > Sales > Sales Documents > Sales Document Header > Define Sales Document Type

7) Explain what is condition types? What is the path to define condition type in SAP for pricing?

The representation of certain aspects related to your daily pricing activities is referred as condition types.

The path for condition type for pricing is

SAP IMG path: SPRO > SAP Reference IMG > Sales and Distribution > Basic Functions > Pricing > Pricing Control > Define Condition Types

8) Mention what is the Reversal PGI? Can you cancel the PGI and mention the transaction code for PGI?

PGI or Post Good Issue is done to keep a record of available goods in stock after the goods are delivered. Good issue transaction cannot be cancelled but can be reversed.

The transaction t-code for reverse PGI is VL09. Partial quantity reversal is not possible, in the delivery document you cannot reverse the PGI for one item/ partial quantity.

9) Explain what is the difference between SAP credit memo request and SAP Credit Memo?

SAP Credit Memo (T-code VF01) is created on the basis of credit memo request (T-code: Va01). Credit memo request is generated when you have to pay to the customer. (Excess bill or damages or change in the price).

10) When would you use a SAP Return Order and SAP Credit Memo?

SAP Return Order is carried out when customer returns any previously purchased products and requires a credit or money back. While credit memo is when the customer is credited without returning any goods.

11) Explain what is SAP Posting Period? What is the transaction code to open and close posting period?

SAP posting period is to make sure that posting period for the business sales order is aligned with financial posting date, which means when financial accounting is ready for closing and proceed with the payment.

The transaction code to open and close posting period is S_alr_87003642

12) Explain what Copy control is and when Copy Control transition can be done? In what manner Copy Control transition can be done?

In SAP SD, the process of copying data from the source document to the target document is done by Copy Controls. They consist of program referred as routing that determines how the system will transfer the data. Copy control could be useful for the end users who don’t want to repeat the control parameters from order- to delivery- and then billing.

Copy control can be done in following manner:

• Sales document by sales document
• Billing document by sales document
• Sales document by delivery
• Sales document by billing document
• Delivery by billing document

13) What are the three levels that copy controls are set up? And what are the transaction codes through which it could be done?

At three levels of sales order copy controls are set up Header level, Item level and Schedule line level.
• VTAA: from sales order to sales order
• VTLA: from sales order to delivery
• VTAF: from the billing document to sales order
• VTFA: from sales order to billing document
• VTFL: from delivery to billing document
• VTFF: from the billing document to billing document

14) Explain how you can include condition type in the pricing procedure?

To include condition type in the pricing procedure, you have to follow the pathway

Basic Functions >Pricing >Pricing Control >Define and Assign pricing procedure and then select “ Maintain pricing procedures” after that select pricing procedure and then “Control Data” and add your condition type to the pricing system.

15) Explain what is Proforma Invoice and what are the types of it?

Proforma invoice is a reference doc for import and export negotiations. The standard proforma invoice doc types are

• With reference to order – F5
• With reference to delivery- F8

16) Mention the transaction code used to create a return delivery?

Transaction code is used to create a return delivery is T/C VA01 with standard order type RE, while return delivery is T/C VL01 with return delivery doctype LR

17) Mention what are the two places where you need to configure CIN (Country Version India)?

The two places where you have to configure CIN is Financial Accounting > Tax on sale and purchase, and other is Logistic General -> Tax on Goods Movement

18) Explain what is the difference between rush order and cash sales?

• Rush Order: Order delivery will be done on the same day while billing will be done later
• Cash Sale: Billing and order delivery will be done on the same day

19) List out the five features you can control for the sale document type?

For sale document type the five features you can control is

• Text
• Partner
• Pricing
• Taxes
• Output
• Delivery

20) Mention what are the techniques available in delivery Scheduling?

The techniques available in delivery Scheduling are

• Backward Scdg: The system calculates requested delivery date
• Forward Scheduling: The system calculates the earliest possible date based on the material available date

asap roadmap phases

ASAP stands for Accelerated SAP. 

 
Its purpose is to help design SAP implementation in the most efficient manner possible.
Its goal is to effectively optimize time, people, quality and other resources, using a proven methodology to implementation.

1- Phase of ASAP Methodology

ASAP focuses on tools and training, wrapped up in a five-phase process oriented road map for guiding implementation.

The road map is composed of five well-known consecutive phases

• Phase 1 Project Preparation
• Phase 2 Business Blueprint
• Phase 3 Realization
• Phase 4 Final Preparation
• Phase 5 Go-Live and support


Brief explanation of each phase



ASAP Methodology – Phase 1 : Project Preparation

Phase-1 initiates with a retrieval of information and resources. It is an important time to assemble the necessary components for the implementation. Some important milestones that need to be accomplished for phase 1 include

• Obtaining senior-level management/stakeholder support
• Identifying clear project objectives
• Architect an efficient decision-making process
• Creating an environment suitable for change and re-engineering
• Building a qualified and capable project team.



ASAP Methodology – Phase 2- Business Blueprint

SAP has defined a business blueprint phase to help extract pertinent information about your company that is necessary for implementation. These blueprints are in the form of questionnaires that are designed to probe for information that uncovers how your company does business. As such, they also serve to document the implementation.

Each business blueprint document essentially outlines your future business processes and business requirements. The kinds of questions asked are germane to the particular business function, as seen in the following sample questions:

1) 1) What information do you capture on a purchase order?

2) 2) What information is required to complete a purchase order?

ASAP Methodology – Phase- 3 – Realization

With the completion of the business in phase 2, “functional” experts are now ready to begin configuring SAP.

The Realization phase is broken in to two parts.



1) 1) Your SAP consulting team helps you configure your baseline system, called the baseline configuration.



1) 2) Your implementation project team fine-tunes that system to meet all your business and process requirements as part of the fine tuning configuration.



The initial configuration completed during the base line configuration is based on the information that you provided in your blueprint document. The remaining approximately 20% of your configuration that was not tackled during the baseline configuration is completed during the fine tuning configuration.



Fine tuning usually deals with the exceptions that are not covered in baseline configuration. This final bit of tweaking represents the work necessary to fit your special needs.




Configuration Testing-
With the help of your SAP consulting team, you segregate your business processes into cycles of related business flows. The cycles serve as independent units that enable you to test specific parts of the business process. You can also work through configuring the SAP implementation guide (IMG). A tool used to assist you in configuring your SAP system in a step by step manner.






Knowledge Transfer-
As the configuration phase comes to a close, it becomes necessary for the Project team to be self-sufficient in their knowledge of the configuration of your SAP system.



Knowledge transfer to the configuration team tasked with system maintenance (that is, maintenance of the business processes after Go-live) needs to be completed at this time. In addition, the end users tasked with actually using the system for day-to-day business purposes must be trained.



ASAP Methodology – Phase 4 – Final Preparation



As phase 3 merges into phase 4, you should find yourselves not only in the midst of SAP training, but also in the midst of rigorous functional and stress testing.



Phase 4 also concentrates on the fine tuning of your configuration before Go-live and more importantly, the migration of data from your old system or systems to SAP.



Workload testing (including peak volume, daily load, and other forms of stress testing), and integration or functional testing are conducted to ensure the accuracy of your data and thestability of your SAP system. Because you should have begun testing back in phase 2, you do not have too far to go until Go-live.



Now is an important time to perform preventative maintenance checks to ensure optimal performance at your SAP system. At the conclusion of phase 4, take time to plan and document a Go-live strategy. Preparation for Go-live means preparing for your end-users questions as they start actively working on the new SAP system.



ASAP Methodology – Phase 5 – Go-live and Support



The Go-live milestone is itself is easy to achieve; a smooth and uneventful Go-live is another matter altogether. Preparation is the key, including attention to what-if scenarios related not only to the individual business processes deployed but also to the functioning of technology underpinning these business processes and preparation for ongoing support, including maintenance contracts and documented processes and procedures are essential.

sap sd pricing procedure

Define Pricing Procedure :

• A pricing procedure is a procedure by where in which you control the execution of condition tyoes in a sequence you would like . It not only executes the condition types but also controls the execution of condition type by the use of requirements , altcv. altcbv, account key.
• In other words, Pricing procedure is a systematic and sequential use of condition types to arrive at a right value of the product.
• To determine the pricing procedure SALES AREA (Sales Organization + Distribution Channel + Division) + CUSTOMER PRICING PROCEDURE (from Customer master) + DOCUMENT PRICING PROCEDURE (from Sales Doc type)
• To view a select the pricing procedure in SPRO which is the standard and copy it and create our own pricing procedure.
• Highlight it and double click the Control icon in the LHS screen.
• We can see that there are 16 columns in the pricing procedure, these are going to be used by the system to control the condition types.
• The detail description of each column is given belo

1. Step:

• • Number that determines the sequence of the conditions with in a procedure.
  • It indicates the position of the condition type in pricing procedure.
  • Ex.: 10, 15 etc.

2. Counter:

• • System uses the counter to count the steps and also it can be used to count mini steps of same condition types. So that number of steps can be reduced in the pricing procedure and hence enhancing the system performance.
  • Access number of the conditions with in a step in the pricing procedure.
  • During automatic pricing, the system takes into account the sequence specified by the counter.

3. Condition Type:

• • It represents pricing element in pricing procedure as a base price, discount, freight and tax.
  • The condition type is used for different functions. In pricing, for example, the condition type lets you differentiate between different kinds of discount; in output determination, between different output types such as order confirmation or delivery note; in batch determination, between different strategy types.
  • Ex.: PR00 - Price, K004 - Material Discount, K005 - Customer/Material Discount, K007 - Customer Discount.

4. Description:

• • System copies description of condition type from its description (V/06).

5. From and 6. To:

•     1. From: This can be used as a base to the condition type for calculating further value.
      2. From and To: The range between the steps from and to can be used to specify the range between same condition types. So that depending upon the condition type, the system deducts or adds the total value of those condition types from specific common source.

7. Manual:

• • This indicator specifies whether the specific condition type can be determined manually during sales order processing.
  • If we check the box then the entry is going to be manual, if we uncheck it, it is going to be automatic.
  • For Base Price and Taxes, the entry should be automatic.
  • For Discounts and Freights, The entry should be manual.
  • If we check the box, in VA01 when we go to conditions at the header/item level, the condition type will not be listed. If we require we will have to manually enter it.
  • If we uncheck the box, in VA01 when we go to conditions at the header/item level, the condition type will be listed.

8. Mandatory:

• • This indicator specifies that particular condition type is mandatory in the pricing procedure.
  • If we check the box, then in VA01 at the header/item level in the conditions tab, if we delete the value in the condition type and try to save the document then system will not allow us to do it and throws an error.
  • If we uncheck the box, then in VA01 at the header/item level in the conditions tab, if we delete the value in the condition type and try to save the document then system will allow us to save it, without giving any error.
  • Mandatory check box should be checked in condition types which are compulsorily required in pricing procedure. Ex.: PR00, MWST.
  • If the condition type is checked with mandatory option, then value should be maintained for that condition type, otherwise the system will not allow the user to process the document.

9. Statistical:

• • This indicator if it is activated will not allow the value of the condition type to be taken into net value calculation.
  • It is used only for information purposes only.
  • This indicator causes a surcharge or discount to be set in the document statistically (that is, without altering the value).
  • This is commonly used for condition types
    • SKTO - Cash Discount
    • VPRS - Cost (Moving average price/Standard Price).

10. Print:

• • The value of this field specifies whether line item can be printed or not in the sales document and at what level it is to be printed.

11. Subtotal:

• • The value of this field determines where the values of subtotals to be captured i.e. in which table and which field.
  • Controls whether and in which fields condition amounts or subtotals (for example, a customer discount or the cost of a material) are stored.
  • If the same fields are used to store different condition amounts, the system totals the individual amounts.
  • These condition amounts or subtotals are used as a starting point for further calculations. You may, for example, want a subtotal of all the discounts included in the pricing of a sales order.

12. Requirement:

• • It is a routine that is written by an ABAP consultant according to the business requirement.
  • By defining Requirement in condition technique we can restrict the access of condition type.
  • To understand the concept, we will take the example of the Rebates. Rebates are to be included during the billing document processing and not in the sales document processing. As rebates are given on the delivered quantity and not on the ordered quantity (in case of cut-off period for rebates).
  • For rebates we use the condition types BO01 to BO05, and in the Requirement column we give the value 24 which is "Only in Billing Document".
  • This Requirement will ensure that these condition types will appear only during the billing document processing.
  • If new Requirements are to be defined we follow the procedure given below.
    • Go to T.Code: VOFM. - Maintain Requirements & Formulas
    • Click on the "Requirements" in the top menu and then click on "pricing".
    • We have a list of requirements, we can ask ABAP consultant to create new requirement based on the client requests.
    • And we assign the application type like V - Sales/Distribution etc.

14. AltCty - Condition formula for alternative calculation type:

• • It is again a Routine that is written by ABAP Consultant.
  • It is an alternative formula for the condition type that can be used instead of standard formulas.
  • For example, let us take the Profit Margin which can be both + / - , so here this routine will help us in generating the value which can be either + or -. Profit margin is not a condition type so it cannot be classified as +ve or -ve in the V/06.
  • Ex.: 950 0 Profit Margin 11.
  • So we assign 11 - Profit Margin.
  • If new routines are to be defined we follow the procedure given below.
    • Go to T.Code: VOFM. - Maintain Requirements & Formulas
  • • Click on the "Formulas" and then on the "Condition Values".
    • We have a list of routines, we can ask ABAP consultant to create new routines based on the client requests.
    • And we assign the application type.

15. AltCBV - Alternative formula for condition base value:

• • Formula for determining the condition basis as an alternative to the standard.
  • It is again a Routine that is written by ABAP Consultant.
  • It is used as a basis to calculate value of the condition type instead of using it from the "FROM" column.
  • Ex.: Freight - KF00.
  • Freight is calculated based on weight, volume etc. and not on the base price. In pricing there is no entry of weight from which the value can be referred like we do for discounts using base price. We have to get the value from the Material master.
  • In this column we can mention the value as 12 - Gross Weight or 13 - Net Weight.
  • During pricing, the system will consider the value that is mentioned in this column and determine the freight based on this value.
  • Suppose we have Net weight: 100 kgs and Gross Weight: 150 kgs. And if we mention 13 in this column then the Freight condition KF00 will be calculated using the weight as 100 kgs.

16. AcyKy - Account Key/ Accrls - Accruals:

• • The values of the Sales Revenues, Sales Deductions, Freight Revenues, Tax Revenues, and Rebate Accruals etc. are going to be posted in the respective G/L accounts in Fi Module.
  • In order to do this we assign account keys/ accruals to the different condition types based on their classification. The classification shown below.
    • ERB Rebate sales deduct.
    • ERF Freight revenue
    • ERL Revenue
    • ERS Sales deductions
    • ERU Rebate accruals
  • For Ex.,
    • For all Price condition types like PR00 etc. we assign ERL - Revenue.
    • For all Discount condition types like K004, K005 etc. we assign ERS - Sales Deductions.
    • For all Freight condition types KF00 etc. we assign ERF - Freight Revenues.
    • For all Rebates condition types BO01 to BO05 we assign in Account key ERB - Rebates Sales deductions and for Accruals ERU - Rebate Accruals.
  • This account keys and accruals are in turn assigned to respective G/L accounts. So the system posts respective values in respective G/L accounts in Fi-Co Module.
  • This also one of the areas of SD - Fi Integration. SD consultants assign the account keys and Fi Consultants assign the respective G/L accounts in T.Code:VKOA.

Inbound idoc configuration steps in sap

What is Idoc :

IDocs are structured ASCII files (or a virtual equivalent). They are the file format used by SAP R/3 to   exchange data with foreign systems.  

 IDocs is the acronym for Interchange Document (Intermediate Document). This indicates a set of (electronic) information which builds a logical entity. An IDoc is e.g. all the data of a single customer in your customer master data file, or the IDoc is all the data of a single invoice. 

The information which is exchanged by IDocs is called a message and the IDoc is the physical representation of such a message. The name “messages” for the information sent via IDocs is used in the same ways as other EDI standards.

Why Idoc Configuration:

To exchange IDoc data between systems and partners that are completely independent or between same systems we need to configure.

Steps in Idoc Configuration:

     Consider we have to exchange data between two different clients.  Following are the configuration steps common for Interchange Documents in both the clients.

   3.1. Create segment

1. Go to transaction WE31 -> Give your segment name -> Press Create. 
2. Type your field name and data element and press save then segment definition will be created automatically.        

  3.2 Create Idoc Type

        Go to Transaction WE30

1. For new IDOC type select the radio button Basic type and press Create button.          
2. Then select the IDOC option to create and press Enter. Give segment name, minimum and maximum number for and save it. Check if this is mandatory segment.      
3. If you want Header and Item create the segment tree according to that, you can view as follows then press Save.     
4. Then go back and set release the IDOC type for using it further. Idoc type will be created successfully once we release that status. We have to release the segments (in WE31) and IDOC type as well. 

  3.3   Create Message Type

Go to transaction WE81 for new message type. Go to change mode and click New Entries for creating our own message type. 

  3.4   Associate Message Type with Basic Idoc Type

Go to transaction WE82 for associating the message type with basic IDOC type. 

  3.5 Create Logical System

Go to transaction SPRO and press SAP Reference IMG for creating the logical system for source and destination.     

Click the node define logical system from SPRO -> SAP Reference IMG -> SAP customizing Implementation Guide -> SAP xApp Resource and Portfolio Management (SAP xRPM) -> Base system Interfaces -> SAP Human Capital Management Integration -> Common system configuration and SAP HCM ALE setup -> Application link enabling (ALE) -> Basic Settings -> Logical Systems -> Define Logical System   

 Else go to transaction SALE then go to Basic settings-> logical system then Define logical system. We can create the same. 

   3.6 Create Logical Connection

1. Go to transaction SM59 for creating Logical Destination.

                   a. SM59 -> logical connections -> Create 

                   b. Then Click Connection test  icon after marking the current user checkbox in logon and security tab.         

                   c.  Then Destination client will automatically open  

3.7 Create Ports

      Go to transaction WE21 for creating ports. WE21 -> Transactional IR -> Create                                   

4. Steps to be done in Source client

 1. Go to transaction SE11 -> create a table with entries.

 2. Go to transaction WE31 -> create segments as shown before. Here you have to mention all the fields mentioned in the database table.

 3. Go to transaction WE30 -> create basic IDOC type and release the segments and basic type.

 4. Go to transaction WE81 -> create message type.

 5. Go to transaction WE82 -> assign message type to basic Idoc type.

 6. Go to transaction BD64 -> Click on Display/change button          

 7. Click on Edit menu -> model view -> create      

 8. Specify description and technical name and press continue.                    

 9. Select your model view -> click edit -> Add message type                  

 10. In dialog box specify sender, receiver, and message type and continue.

 11. Click on environment menu -> generate partner profile               

  12. It will show the following screen. Select your model view and click on execute.      

  13. It will show the partner profile log in next screen.

  14. Click on back button 2 times it will take to distribution model screen.

  15. Click on Edit -> Model view -> Distribute

  16. In displayed dialog box select the partner system and continue.

   17. Then it will show the log of model view distribution.

   18. To check partner profile go to transaction WE20.

   19. Then write the report program in SE38 to create IDOC control records and transfer it to destination   partner system.

   20. Go to Transaction WE02 to check the generated IDOC control records. 

5. Steps to be done in Destination client

1. Go to transaction SE37 to create the function module for updating the table from IDOC segments.
2. Specify import, export and table parameters.
3. Go to transaction WE57 for assigning the FM to logical system. Click on Display/ change button.
4. Specify FM name, function type, basic type(IDOC ), message type and direction then save it.
5. Go to transaction BD51 to define input method for inbound function module and click on Display change button
6. Specify your function module and input type by clicking the new entries.
7. Go to transaction WE42 and  create process code.
8. Go to transaction BD64 and generate the partner profile again.
9. Got to transaction SE 38 and execute the transaction in source system (client100).
10. Check in destination system (client 800). Go to Transaction WE02 and check your table in SE11. (You can get the transferred entries in that table).