SAP ABAP IMG Activity ISMSD_IAC_ORDER_DEF (Define Variants of IAC Subscription Sales)

Hierarchy

☛

IS-M (Software Component) SAP MEDIA
⤷

IS-M (Application Component) SAP Media
⤷

JSD (Package) Appl. dev. R/3 Publishing Sales and Distribution System

IMG Activity

ID	ISMSD_IAC_ORDER_DEF	Define Variants of IAC Subscription Sales
Transaction Code	S_KK4_82000093	(empty)
Created on	20000216
Customizing Attributes	ISMSD_IAC_ORDER_DEF	Define Variants of IAC Subscription Sales
Customizing Activity	ISMSD_IAC_ORDER_DEF	Define Variants of IAC Subscription Sales

Document

Document Class	SIMG	Hypertext: Object Class - Class to which a document belongs.
Document Name	ISMSD_IAC_ORDER_DEF

In this step, you maintain the control parameters for the IAC Subscription Sales. You also define a set of fixed order values and a set of variable order values for each record, represented by its key. Each line in this Customizing table describes a complete attribute of the Internet application Subscription Sales.

Requirements

Before you perform this step, you must work through the steps Identification and Checking of Business Partners, Maintenance of Combinations of Fixed Order Values and Maintenance of Combinations of Variable Order Values (Preassignments).

Activities

Maintain the required data under a key of your choice. You specify this key when you call up the Internet application by attaching it to the URL; the key represents an attribute of the Internet application.

Specify a description for the variant. This is simply used to identify the variant and does not affect processing in any way. For example, you might describe the basic process of the variant.
Specify the key that references the set of fixed order values required in this attribute.
Specify the corresponding key for the variable order values.
Select the Ship-To Party Required indicator if the variant has to contain a ship-to party other than the sold-to party. If you want it to be possible (but not necessary) to specify an alternate ship-to party in the variant, this indicator must not be selected. All that is required is to display the corresponding fields on the Web form (HTML template). For example, you can select the indicator if a subscriber is to be awarded a gift for donating their subscription and the recipient of the subscription cannot be the sold-to party.
Select the Bill-To Party Required indicator if the variant has to contain a bill-to party other than the sold-to party. Here too, the indicator must not be selected if the alternate bill-to party is to be optional. In this case you only need to display the fields on the Web form.
Select the indicator Sales Agent not Sold-To Party if it is possible to specify a sales agent when creating an order in the IAC using this variant, but the sales agent cannot be the sold-to party in the order. This setting relates to sales support. You can make further settings indirectly by specifying the sales source and sales promotion in the fixed order values for this variant (for example, whether or not a gift is awarded in exchange for obtaining a subscription and which gifts are available).
You use the keys to settings for identification and checking of business partners to define how a business partner already known in the system can log on to the system in a certain role. The user can log on by accessing the logon screen from the order form, i.e. the means of accessing the logon screen must be displayed on the Web form, represented by a button.
You must specify a key of this kind for each of the four roles recognized in the IAC: sold-to party, ship-to party, bill-to party and sales agent. The keys allow you to specify that different data is used for identification and checking depending on the business partner role, for example the customer number and password of the Internet user for logon as a sold-to party and no check at all for logon as a sales agent.
You maintain the data required in the step 'Identify and Check Business Partner'.
If you do not want to use a certain role in a particular variant of the IAC (for example, not display the bill-to party fields on the order form) or if you do not want to allow known business partners to log on explicitly, you can leave the relevant fields blank. In the latter case, the duplicate check identifies any business partners that already exist in the system. If a duplicate is identifies, the system responds as specified in the field 'Data Destination'.
Note: You can also identify business partners directly on the order form. The fields Alias/User Name, BP No. and Password can be used for this in the role of sold-to party (the user has to enter the Internet password defined when a previous online order was placed). If the Internet user is switched from an SU05 to an SU01 user, the customer number is also accepted in the field Alias/User Name for customers who have an Internet user based on transaction SU05. This means it is possible to log on to the order form directly with two fields during the switch. The field BP No. can be displayed on the Web form for the role Sales Agent, so that the sales agent or gift recipient can be identified directly (without a check), for example, if they are themselves a reader and have introduced a new customer.
You can define what is to be done with the data from the Internet in the field Destination for saving Internet data. You can store all data in the temporary table. However, if you do this you will have to postprocess all the data using report RJKWWWTEMP. You can also create business partners and orders immediately automatically for correct data (from the perspective of M/SD) and record duplicates or errors in the temporary table or reject them.
You select the indicator Save credit card data with BP if you want to save credit card data not only with the new order but also with the business partner.
If you want to record a limited subscription, define the validity period of the subscription in days or in copies.
Maintain an initial country. This allows you to define a 'domestic' variant of the application - the country fields in the business partner addresses should then be hidden and the selection fields for the region or state are then filtered accordingly. The specification of the initial country can also be used for a preassignment in the selection box on the HTML page.
In the User Name field, specify how the user name is to be determined for the customer's Internet user. This setting is only relevant if you are using the Internet user based on transaction SU01 (see the corresponding Release note). The user name can either be defined by the customer or created by a function module. Enter the function module in the field Function Module for User Name.
Specify how the password for the customer's Internet user is to be determined and communicated. If the customer is to be sent their password via e-mail, you must set up the communication interface required for this purpose.
Specify how the connection between the IAC and a CRM mail campaign is to be set up. This setting is only relevant if you use the CRM Media solution. The setting defines the behavior of the IAC if it is called up from a CRM e-mail campaign. You can assign default entries for various fields or log the customer on.
In the field Role of CRM Business Partner, specify the role in which the customer's data is to be entered as default if the IAC is accessed from a CRM e-mail campaign. For example, you could use an e-mail campaign to invite an existing customer to introduce third parties as new subscribers. This would mean the customer would appear in the role of Sales Agent in an order that resulted from the campaign.
Specify whether or not a log record is to be created when an order is created directly via the IAC or later in postprocessing.
Specify the account groups for the sold-to party, ship-to party, bill-to party and sales agent. This setting also controls whether or not the corresponding business partners have to be created with a contract account (use of FI-CA). If you do not specify an account group here, the system determines the account groups from the general control parameters for Sales.
Enter the accepted coding status of an address. This allows you to define how a business partner address entered in the Internet must be coded before it is accepted by the system. If you do not make an entry here, the system accepts all addresses that have a coding status of 'Not coded' or better. This was also the standard rule up to release 4.71.

Further notes

As explained above, each row you fill in in this step creates a variant of the Internet application Subscription Sales. You must design the HTML templates according to this variant (you can design these in various ways using themes - see IAC docume

Business Attributes

ASAP Roadmap ID	204	Establish Functions and Processes
Mandatory / Optional	1	Mandatory activity
Critical / Non-Critical	1	Critical
Country-Dependency	A	Valid for all countries

Assigned Application Components

Documentation Object Class	Documentation Object Name	Current line number	Application Component	Application Component Name
SIMG	ISMSD_IAC_ORDER_DEF	0	I170007124	Order

Maintenance Objects

Maintenance object type

Customizing Object

Assigned objects
Customizing Object	Object Type	Transaction Code	Sub-object	Do not Summarize	Skip Subset Dialog Box	Description for multiple selections
TJKWWW_CONTROL	S - Table (with text table)	SM30

History

Last changed by/on	SAP	20000310
SAP Release Created in

Object Hierarchy

Used by

Advertise Links