IS RETAIL

[Former Member]

hey ,

can u guys help me in providing information regarding

subsequent settlements

configuring agreement types

configuring condition type groups and its assignment

[Former Member]

hi shilpa,

Configuring Communication Channels with Adapter Type WS

Use

With the communication channel for which you have implemented the adapter type WS, you can configure the communication using Web service runtime.

Depending on whether you want to configure a Web service consumer or Web service provider, use the sender or receiver channel (adapter WS).

You can use a communication channel for which you have implemented the adapter type WS for direct communication between two business systems, as well for enhanced communication using the Integration Server.

● Use a receiver channel for direct communication and assign it to a direct connection.

In this case the sender system functions as Web service consumer and the receiver system as Web service provider.

More information: Configuring Direct Communication

● For communication using the Integration Server you require a sender or a receiver channel, depending on whether you want to configure the inbound processing of the outbound processing in the Integration Server.

If you configure inbound processing in the Integration Server, the sender system functions as Web service consumer and the Integration Server as Web service provider.

If you configure outbound processing in the Integration Server, the Integration Server functions as Web service consumer and the receiver system as Web service provider.

More information: Configuring Integration Server Communication

In the following graphic shows the configurable communication scenarios and the relevant configuration objects.

Procedure

1. Creating a Communication Channel, Specifying a Direction and Adapter Type

First create the communication channel, specify whether it is to be a sender or receiver channel and choose the adapter type WS.

For more general information on how to create a communication channel, see Defining Communication Channels.

The following are default attributes:

● Transport Protocol: HTTP 1.0

● Message Protocol: WS 1.0

● Adapter Engine: Integration Server

2. Define Type of Web Service Call

...

The type of Web service call specifies whether the call is made locally (same logical system), or remotely (different logical system). Depending on your choice, select or deselect the checkbox Local Call.

You can only configure this setting for a receiver channel.

The call type you select determines which other attributes you can define.

3. Specifying Further Attributes for Local or Remote Calls

Configuring Local Calls

Specify the following attributes for a local call.

Technical Transport Settings

Input Field

Description

Transport Binding

The default value is SOAP 1.1 Using HTTP.

More information: http://www.w3.org/TR/2000/NOTE-SOAP-20000508/#_Toc478383526.

...

Settings for Web Service Addressing

You use these settings to determine how the Web service call can be addressed independently of a transport protocol.

Input Field

Description

Protocol

Specifies protocol for Web service addressing

The default value is WS-A

Reference Parameters (Server)

Input field for parameters that are to be specified with the Web service call and that can be used to identify the Web service call.

The information specified here is in the SOAP header of the message.

Enter the parameters as strings.

You can specify a reference parameter if necessary.

More information about Web service addressing: http://www.w3.org/TR/ws-addr-core/.

Settings for Handling Message Attachments

Input Field

Description

Process Non-Modeled Attachments checkbox

Specifies whether non-modeled attachments are to be transferred with the message.

Non-modeled attachments are attachments that are appended to the message as an HTTP or MIME attachment.

Modeled attachments are appended directly in the message.

Configuring Remote Calls

Specify the following attributes for a remote call.

...

Security Settings

Input Field

Description

Authentication Method field

Specifies whether the sender has to authenticate itself with the service provider, and if so, how.

You can choose between the following functions:

● User ID/Password (Authentication on HTTP Level)

● Authentication with X.509 SSL Client Certificate (Using HTTPS)

More information: Client Certificates

● Authentication with logon ticket (HTTP Level)

More information: Logon Tickets

● Authentication with X.509 SSL Client Certificate (authentication in message)

More information: Client Certificates

● Authentication with X.509 SSL Client Certificate SAML 1.1 Sender Vouches Assertion (authentication in message)

More information: Configuring Principal Propagation (SAML).

Technical Transport Settings

Input Field

Description

Transport Protocol

Specifies the required transport protocol (HTTP or HTTPS).

Target Host

Specifies the name of the target machine

Service Name/Port

Specifies the port for the target machine

URL Access Path or Target Client

If the target system is an SAP system (ABAP-based), specify the client (field Target Client (ABAP stack)).

In this case you must also enter the logon language in the target system.

If you configure a sender channel, this attribute is set for the input of a target client (ABAP stack) because in this case you are addressing the Integration Server in the channel.

If the target system is not an SAP system (ABAP-based), enter the URL (access path) for the target system (field URL Access Path).

Either enter the URL as WSDL URL or as an access URL, depending on how you want to implement the channel.

- Enter a WSDL URL if you want to use the communication channel to configure the outbound processing of the Integration Server. In this case assign the channel later to a receiver agreement. The Integration Server functions at runtime as Web service consumer and requires the WSDL URL at configurations time to be able to access the WSDL document. The web service consumer configuration for the Integration Server is basically based on the information in the WSDL document.

- Enter an access URL if you want to use the communication channel for direct communication. In this case assign the channel later to a direct connection. The sender functions at runtime as Web service consumer and required the access URL to be able to execute the call to the Web service provider (receiver).

Access Path Points to a WSDL

(Use of Channel in Receiver Agreement)

Select this checkbox if you want to use the communication channel for enhanced communication. The URL is then categorized as a WSDL URL.

If you select this checkbox, the communication channel cannot be used for direct connection.

Optimized XML Transfer

Specifies whether the message is to be converted to a special format to speed up transfer.

The following values are possible:

● No Optimization

● Binary MTOM XML Format

If you select this entry, the message will be transferred using the MTOM (Message Transmission Optimization Mechanism) standard. This means that binary data of type base64Binary is stored in a message attachment (XOP attachment) for transferal, and does not need to be decoded separately.

More information: SOAP Message Transmission Optimization Mechanism (MTOM)

More information:

http://www.w3.org/TR/soap12-mtom/

● Binary SAP-XML Format

If you choose this entry then the message will be optimally transferred based on an SAP-own format.

The performance improvement can be seen like this:

○ If the same day appears repeatedly in the payload then the day is only given completely in the first position. In all further positions in the payload only a reference to the day is given.

○ If the payload contains binary parts then, according to base64Binary, these must not be converted separately. This is because when using the binary XML format XML data is not transferred, only binary data.

Transport Binding

The default value is SOAP 1.1 Using HTTP.

More information: http://www.w3.org.

Server Side Session Timeout

Specifies time (in seconds) after which the connection in state management is canceled.

Reliable Messaging Settings

You use these settings to define the reliable transferal of asynchronous messages, based on the standard WS-RM protocol.

Input Field

Description

Acknowledgment Interval

Specifies a time interval (in seconds) in which the receiver (Web service provider) has to confirm receipt of a message.

Protocol

Specifies the protocol for Web Services Reliable Messaging (WS-RM).

The default value is WS-RM 2005/02.

More information: http://specs.xmlsoap.org/ws/2005/02/rm/ws-reliablemessaging.pdf.

Settings for Web Service Addressing

Proceed as described for the local call.

Settings for Handling Message Attachments

Proceed as described for the local call.

for subsequent settlements

abap.wikiprog.com/wiki/BAPI_SINGLEREMUREQS_CHANGEMULT - 23k -

abap.wikiprog.com/wiki/BAPI_SINGLEREMUREQS_CREATEMULT - 23k

Subsequent Settlement: Retrospective Business Volume Update

Use

If you have entered arrangements or conditions retrospectively (see Subsequent Settlement: Retrospective Creation of Arrangements), you must retrospectively update the values for business volume achieved, so that the system takes all business volume into account during settlement accounting.

Business volume can be updated subsequently with this function.

Prerequisites

All the relevant documents must be included in the document index (LIS information structure S111). You can check this as follows in the Data Browser (Tools ® ABAP Workbench, then Overview ® Data Browser):

Enter table S111 and choose Table contents.

In field BLTYP (document category), enter value 01 (purchase order/scheduling agreement), 30 (vendor billing document) or 40 (settlement request), and in field VRSIO (version), enter LIS version 000.

Enter the document item you wish to examine in the fields BELNR (Document number) and POSNR (document item) fields and choose Execute.

This function can only process the document if the system displays several table entries. For information on how you recompile the document index, see Subsequent Settlement: Retrospective Compilation of a Document Index.

Features

The system updates the information structures of Subsequent Settlement, that is, all information structures for which active update rules exist for the update group 000029. In the standard SAP system, these are the information structures

- S074

Operative view (business volumes and income used for settlement accounting purposes)

- S015

Standard information structure for analysis (standard analysis, planning, etc., if activated by you)

You can initially carry out a test run in order to view any error messages that may be generated and correct any errors.

You can specify that the execution of the program is terminated or interrupted by a certain point in time.

If required, the system issues a log containing the business volumes that have been updated for the arrangement, and any error messages that occurred.

An analysis function enables you to generate a list output of all document items, any associated follow-on documents, and one or more notes on the course of the updating process. Among other things, this shows you which document items are contained in the document index (S111) and why updating was or was not carried out.

Activities

For information on how to carry out retrospective updating, please see Subsequent Settlement: Carrying Out Retrospective Business Volume Update.

Constraints

Because this function does not redetermine prices, does not carry out a new valuation, and does not make any changes to the document items, the following functional constraints exist:

Condition exclusions may not be processed correctly. You should therefore not work with condition exclusions if you are using this function.

The valuation of the document remains unchanged. In particular, the system does not post any provisions for accrued income.

The following examples illustrate the problems may liable to occur:

A rebate at corporate group level has been entered against condition type A001 (rebate arrangement 1), which is designed to take precedence over a condition requiring subsequent settlement belonging to condition type A002 (rebate arrangement 2) of the procuring regional purchasing organization. Since no adjustment of the document conditions takes place (in particular, no price determination) the exclusion cannot be taken into account.

The condition record A002 (rebate arrangement 2, regional incentive rebate) is included in the document conditions. A condition record belonging to condition type A001 (rebate arrangement 1, incentive rebate at corporate group level) is now subsequently determined. The business volume update for the condition record belonging to condition type A002 ought to be canceled due to the condition exclusion. It may also be necessary to reverse any posting to provisions for accrued income, re-valuate the purchasing document, and post appropriate follow-on documents. However, none of this occurs. The update remains effective despite the infringement of the condition exclusion.

The immediate vendor discount RL01 should only be valid if no subsequent rebate is granted. If such a rebate is determined retrospectively, the vendor discount ought to be canceled (new valuation, follow-on documents). The ensuing changes in the subtotals could have far-reaching effects. The vendor discount therefore remains unchanged

thanks

karthik

reward me points if usefull

[Former Member]

Hi,

Check this.

Customizing settings

1. Maintain Business volume comparison type

SAP Customizing Implementation Guide>>Materials Management>>Purchasing>>Subsequent (End-of-Period Rebate) Settlement>>Agreements>>Define Business Volume Comparison Type.

Copy standard Business volume comparison type and maintain Business volume comparison ‘OPTIONAL’ for partial and final settlements

2. Define Rebate Arrangement Types for Subsequent Settlement

SAP Customizing Implementation Guide>>Materials Management>>Purchasing>>Subsequent (End-of-Period Rebate) Settlement>>Agreements>> Define Rebate Arrangement Types for Subsequent Settlement

a. Copy standard ‘Rebate Arrangement Types’

b. Maintain the newly created ‘Business volume comparison type’

c. Maintain settlement schema

3. Define Condition Type Groups for Rebate Arrangements

SAP Customizing Implementation Guide>>Materials Management>>Purchasing>>Subsequent (End-of-Period Rebate) Settlement>>Agreements>> Condition Type Groups>> Define Condition Type Groups for Rebate Arrangements

Create new condition type group

4. Assign Condition Type/Table to Condition Type Group

SAP Customizing Implementation Guide>>Materials Management>>Purchasing>>Subsequent (End-of-Period Rebate) Settlement>>Agreements>> Condition Type Groups>> Assign Condition Type/Table to Condition Type Group

Assign condition type (A001 or A001) to the newly created Condition Type Group

5. Assign Condition Type Groups and Arrangement Types

SAP Customizing Implementation Guide>>Materials Management>>Purchasing>>Subsequent (End-of-Period Rebate) Settlement>>Agreements>> Condition Type Groups>> Assign Condition Type Groups and Arrangement Types

6. Assign Condition Type Groups and Arrangement Types

SAP Customizing Implementation Guide>>Materials Management>>Purchasing>>Subsequent (End-of-Period Rebate) Settlement>>Agreements>> Condition Type Groups>>Assign Condition Type Groups and Arrangement Types

Transactions:

1. Create Agreement (MEB1)

a. Enter vendor

b. Maintain conditions

c. Maintain scales

2. Do PO/GR/IV

3. Business volume comparison (MEB3)

a. enter agreement number

b. Go to Settlement>>Business volume comparison

Comparison update

4. Settlement (MEB4)

a. Enter Settlement date

b. Agreement date

Regards,

Shakthi.