Billing plan type determination based on Variant configuration characterist

Hi All,
We have a process where in to determine the Billing plan of the contract based on the Characteristic value of the material.
If the characteristic value is 'M' Monthly billing plan and assign corresponding billing plan to FPLA, if value is 'Q' then quarterly.
what is the right place to update the FPLA table and further getting FPLT updated automatically.
We tried doing the code in MV45AFZZ, VBKD routing.. But the FPLT is not getting updated all the time.
Thanks,
Ajai.

Prathiba
Are you able to resolve this issue?

Similar Messages

About billing plan types

Sir ,
I have a need of Billing plan type configuration step by step,i have tried to configure throgh glenc willams but i couldn't able to understand.
Kindly send me the configuration of billing plantypes and explain me in which situation these are applicable.
Thankig u

Milestone billing means distributing the total amount to be billed over multiple billing
dates in the billing plan.
As each milestone is successfully reached, the customer is billed either a percentage of
the entire project cost or simply a pre-defined amount.
During sales order processing, the system determines from the item category whether a
billing plan is required and, if so, which type of plan
The type of billing plan that is determined at this point is set up in Customizing and
cannot be changed in the sales document.
Billing plans for periodic billing and milestone billing plans for project-related milestone
billing have different overview screens so that you can enter data relevant to your
processing.
For example, for milestone billing, you must be able to enter data to identify the
individual milestones.
IMG configuration requires :-
1. Maintain billing plan types for milestone billing in OVBO.
2. Define date description in SM30 - V_TVTB.
3. Maintain Date Category for Billing Plan Type IN OVBJ.
4. Allocate date category in SM30 - V_TFPLA_TY.
5. Maintain date proposal for Billing Plan Type in OVBM.
6. Assign Billing Plan Type to Sales Documents Type in OVBP.
7. Assign Billing Plan Type to Item Categories in OVBR.
8. Define rules for determining the date in OVBS.
Milestone billing is typically used for billing projects, such as plant engineering and
construction projects. Such projects often include a series of milestones that mark the
completion of different stages of the work. In the SAP R/3 System, milestones are defined
in a network along with planned and actual dates for the completion of work. The milestones
are also assigned to the billing dates in the billing plan.
Each milestone-related billing date is blocked for processing until the Project System
confirms that the milestone is completed.
Delivery-relevant order items for which a milestone billing plan applies are billed on the
basis of the requested delivery quantity and not on the total of the confirmed quantities.
The connection between the project and the sales document item is made in the individual
schedule lines of the item. Each schedule item can be assigned to a network in a project.
To display the project-related data for a schedule line, proceed as follows:
In one of the overview screens of the sales document, select
1. Item -> Schedule lines.
2. Mark the schedule line and select Procurement details.
The following figure shows an example of milestone billing where only the Contract have
been billed :
Order Item Turbine 100,000
Billing Plan
Billing date Description % Value Billing Block Milestone Billing Status
01-10-94 Contract 10 10,000 - x x
01-03-95 Assembly 30 30,000 x x
01-04-95 Maintenance 30 30,000 x x
01-05-95 Acceptance 30 30,000 x x
01-06-95 Final invoice .. .. x
Network/Activities
Milestone Estimate Actual
Assembly 01-03-95 01-03-95
Maintenance 01-04-95
Acceptance 01-05-95
For each billing date in a milestone billing plan, you can specify whether the billing
date is:
1. fixed
2. always updated with the actual date of the milestone
3. updated with the actual date of the milestone, if the date is earlier than the
planned billing date for the date

Define dateline category during maintenance of billing plan type

Hi, I am in the midst of setting up the SD configuration in my current system from scratch and this is the error message that I have encountered, "Define dateline category during maintenance of billing plan type". Basically, what I have done is to create a contract using tcode 'VA41'. This error happened on the second screen after inserting contract type, sales org, distribution channel and division. any guru out there, pls advise. Thanks!!!
Regards
Andy

Hi!! Andy,
Dateline category controls data such as the billing block and the billing rule at the billing date level of the billing plan.
We assign a date category to billing plan in t.code OVBJ. check the assignment, make them if neccessary.
Hope this will solve your problem.
Regards,
PATHIK
Dear Andy,
Please check & maintain the enteries in t.code OVKK.
Do give your feedback.
Regards,
PATHIK
Message was edited by:
Pathik Pandya

Printing PO error "Maintain billing plan type in sales document type...

Hi,
I am trying to print SAPscript to pdf using ADOBE_ENTRY_NEU routine and when i try to display output from ME9F, i get an error that says "Maintain billing plan type in sales document type or Item Category"
anyone have any clue why this is happening?

As this is about SAPscript, moved it to ABAP Programming forum

Problems with bill copying control and materials with variant configuration

Hi experts,
I have a problem with a bill copying control and the way that my customer is trying to create and print the Bill (VF01).
Let me explain...They have in a Sales Order a material with variant configuration per position, each one can have many characteristics. This characteristics must be printing on the billing document, creating different bills 'coz the max. lines number is 18, so the bill must change page per material-characteristics.
Example:
Max. Number Lines = 3
Position 10
Material A
     -Characteristic A
     -Characteristic B
     -Characteristic C     (Bill 1)
     -Characteristic D
     -Characteristic E
     -Characteristic F     (Bill 2)
Position 20
Material B
     -Characteristic A     (Bill 3) counting characteristics upside
     -Characteristic B
     -Characteristic C
     -Characteristic D     (Bill 4)
I created on Tx VOFM (Data Transfer-Billing documents) a routine trying to control this jump, but my problem is when I'm creating the Bill document (VF01) this work only by position, the debugging enter per position.. so I don't have any control to tell the program must count the characteristics and create another bill.
So... Somebody can help me..or have any idea to solve this problem.....
Thxs a lot!!!!
Diego Helfer

HI Diego
For our coming assignment, we do have similar sort of situation. Currently we are in Requirements Gathering phase.
Though we do not have Variant Configuration in place, we do have restriction for no..of items to be used for printing in Billing Documents.
Current proposal is that we will restrict at Sales Order Creation. If the number of items are increasing, we will restrict saving the document and loading has to be done again. As itz better to restrict at initial phase.
Our schema is One Sales Order -> One Delivery -> One Billig Document.
   Will post if we can manage to acheive some other way and do request you the same.
Kind Regards
Eswar

SD Variant Configuration - characteristic value computation

Hi Everyone
Greetings from Vinod
i am creating a variant material which has 3 characteristics. out of the 3 characteristics, 2 are inputed by the user and the third characteristic needs to be populated with the difference of the 2 chatacteristic values that we have entered before. is there a standard setting that we have to maintain, or should we do a custom development on the same. the third characteristic value which is computed based on the difference of the precious two characteristic will then derive pricing of the variant material. please throw some suggestions and inputs in this discussion.

Hi,
calculating values of characteristics is done with so-called dependencies.
In a dependency you can define the rule how a value should be calculated.
You have to create a class of class type 300 and assign your characteristics to this class.
Assign the class to a material of material type "Configurable Materials".
Open the material with transaction PMEVC (Modeling Environment for Variant Configuration).
There you maintain a dependency of type procedure.
The source code may look like this for your example:
$SELF.CHARACTERISTIC_3 = CHARACTERISTICS_1 - CHARACTERISTIC_2
You can find details for variant configuration on help.sap.com:
http://help.sap.com
-> SAP ERP
-> SAP ERP Central Component
-> Logistics
-> Logistics - General
-> Variant Configuration (LO-VC)
Details on transaction PMEVC (Modeling Environment for Variant Configuration):
http://help.sap.com
-> SAP ERP
-> SAP ERP Central Component
-> Logistics
-> Logistics - General
-> Variant Configuration (LO-VC)
-> Modeling Environment for Variant Configuration
Information on dependencies:
http://help.sap.com
-> SAP ERP
-> SAP ERP Central Component
-> Logistics
-> Logistics - General
-> Variant Configuration (LO-VC)
-> Dependencies
and
-> Dependency Syntax: General Rules
Best regards,
Sebastian

Billing plan type

hi
i am trying to process a billing plant with mile stone billing where a customer pays a down payment 0009 and then pays the rest of the amount after delivery 0008.
the customer puts a down payment of 10% or 100
when i try to process it with 0008 closing invoice it brings in the complete amount of $1000 instead of $900
how am i supposed to handle such requests? am i doing the right thing?

Hi
If you want to have down payment of 10% and the rest 90% in the final invoice then there is no need to process down payment request using the billing type FAZ. You can directly process the down payment with the billing type F2 instead of FAZ.
If you want to use down payment request process seperately then we need to clear the down payment in the final invoice by reducing the 10% from the final value and adjusting it against the already posted down payment in the FI since the down payment request will posted with special GL indicator in FI.
So you can either choose to have down payment process (10% + 100%) or a simple process of having down payment and final invoice (10% + 90%).
Regards
Rajkuamr K

Billing document type in billing plan

Hi Guru's,
I am configured down payment process.
when creating a sales order , for a line item --> billing plan tab --> Billing type FAZ is automatically picked.
Can any one suggest me the configuration steps to determinate the customized billing type ZFAZ , which should be picked instead of standard FAZ.
Please suggest
thanks
Gopalkrishna

Dear Gopalkrishna,
Please check the date categories for billing plan type in transaction OVBJ.
You can set the proposed billing type (TFPLT-FKARV) there.
Best regards,
Csaba Soltesz

Default Billing Type in Billing Plan

Hi,
How do I change the default billing type in my billing plan?
Thanks!

Hi
Goto T Code OVBJ (SPRO>SD> Billing> Billing plan>Define and assign date category).
Select your billing Plan type and corresponding Date category.
On next screen u can change/set default Billing Type, Billing block and Billing rule.

Regarding billing plans

Hi friends... please ssuggest me the configuration steps of periodic billing and mile stone billing... please send me if possible the configuation steps to my mail id [email protected]

Hi Durga Prasad,
Periodic Billing
Periodic billing means billing a total amount for each individual billing date in the plan. For example, if you are creating a rental contract, the system can propose a schedule of monthly rental payments, according to the length and conditions of the contract.
Milestone Billing
Milestone billing means distributing the total amount to be billed over multiple billing dates in the billing plan. For example, you can use a billing plan for billing a make-to-order item that is assigned to a project in the SAP Project System. When you enter the project-related make-to-order item in the sales order (or assembly order), the system proposes a billing plan based on milestones defined for networks in the project. As each milestone is successfully reached, the customer is billed either a percentage of the entire project cost or simply a pre-defined amount.
1) Periodic Billing
Periodic billing can be used, for example, in rental contracts. The billing dates in a periodic billing plan can be determined from the following sources:
=> Control data in the billing plan
=> Header data in the rental contract
=> Manually entered dates
The following dates are important for billing date determination:
=> Start and end dates
=> Period (monthly, quarterly, annually)
=> Horizon
Start and end dates
Start and end dates define the duration of the billing plan and, whenever possible, are copied from the start and end dates of the corresponding rental contract. Depending on the configuration of your system, these dates may be indirectly determined by the system. For example, the contract start date may be determined automatically as soon as the installation date is entered.
Period (monthly, quarterly, annually)
The periodicity of the billing dates determines the frequency with which the billing dates are created in the billing plan and, in addition, whether a billing date is processed for billing on the first or last day of the month.
Horizon
In case no end date is entered, or the end date lies so far in the future that not all billing dates can established, then a rule for determining the horizon can be entered. The horizon for periodic billing determines the last date of the billing plan.
The horizon is always determined by a rule that uses the current date as a baseline. If the current date is updated during processing, the system automatically extends the horizon and the schedule of billing dates into the future.
2) Milestone Billing
Milestone billing is typically used for billing projects, such as plant engineering and construction projects. Such projects often include a series of milestones that mark the completion of different stages of the work. In the SAP R/3 System, milestones are defined in a network along with planned and actual dates for the completion of work. The milestones are also assigned to the billing dates in the billing plan. Each milestone-related billing date is blocked for processing until the Project System confirms that the milestone is completed.
Delivery-relevant order items for which a milestone billing plan applies are billed on the basis of the requested delivery quantity and not on the total of the confirmed quantities.
For each billing date in a milestone billing plan, you can specify whether the billing date is:
=> fixed
=> always updated with the actual date of the milestone
=> updated with the actual date of the milestone, if the date is earlier than the planned billing date for the date
=> updated with the actual date of the milestone, if the date is earlier than the planned billing date for the date
As of Release 3.0C it is also possible to assign milestones to the dates of the billing plan during milestone billing if no network plan has been opened.
In order to do this you must assign the milestone manually in billing plan maintenance. For you to be able to make this assignment, the Fixed date field of the proposed date category of the billing plan type must not be blank. The additional fixed value (as of Release 3.0C) of Fixed date means that you cannot assign it to a milestone. Milestone assignment is possible for all other values. You make these settings in the Implementation Guide.
For configuration please find the below path:
IMG --> Sales and Distribution --> Billing --> Billing Plans
Please Reward If Really Helpful,
Thanks and Regards,
Sateesh.Kandula

Billing planes

Friends,
How Billing planes (Milestone) can be used in the down payment processing?
Here we are collecting 30% payment during sales order creation & 70% during shipment.
Thanks

Hi Friend,
Mile stone billing is part of PROJECT SYSTEMS MODULE integrated with SD.
Milestone billing is practiced by Infrastructure companies and Power Ind,and construction industry(projects).
Billing Plan for Milestone Billing
Milestone billing means distributing the total amount to be billed over multiple billing
dates in the billing plan.
As each milestone is successfully reached, the customer is billed either a percentage of
the entire project cost or simply a pre-defined amount.
During sales order processing, the system determines from the item category whether a
billing plan is required and, if so, which type of plan
The type of billing plan that is determined at this point is set up in Customizing and
cannot be changed in the sales document.
Billing plans for periodic billing and milestone billing plans for project-related milestone
billing have different overview screens so that you can enter data relevant to your
processing.
For example, for milestone billing, you must be able to enter data to identify the
individual milestones.
IMG configuration requires :-
1. Maintain billing plan types for milestone billing in OVBO.
2. Define date description in SM30 - V_TVTB.
3. Maintain Date Category for Billing Plan Type IN OVBJ.
4. Allocate date category in SM30 - V_TFPLA_TY.
5. Maintain date proposal for Billing Plan Type in OVBM.
6. Assign Billing Plan Type to Sales Documents Type in OVBP.
7. Assign Billing Plan Type to Item Categories in OVBR.
8. Define rules for determining the date in OVBS.
Milestone billing is typically used for billing projects, such as plant engineering and
construction projects. Such projects often include a series of milestones that mark the
completion of different stages of the work. In the SAP R/3 System, milestones are defined
in a network along with planned and actual dates for the completion of work. The milestones
are also assigned to the billing dates in the billing plan.
Each milestone-related billing date is blocked for processing until the Project System
confirms that the milestone is completed.
Delivery-relevant order items for which a milestone billing plan applies are billed on the
basis of the requested delivery quantity and not on the total of the confirmed quantities.
The connection between the project and the sales document item is made in the individual
schedule lines of the item. Each schedule item can be assigned to a network in a project.
To display the project-related data for a schedule line, proceed as follows:
In one of the overview screens of the sales document, select
1. Item -> Schedule lines.
2. Mark the schedule line and select Procurement details.
The following figure shows an example of milestone billing where only the Contract have
been billed :
Order Item Turbine 100,000
Billing Plan
Billing date Description % Value Billing Block Milestone Billing Status
01-10-94 Contract 10 10,000 - x x
01-03-95 Assembly 30 30,000 x x
01-04-95 Maintenance 30 30,000 x x
01-05-95 Acceptance 30 30,000 x x
01-06-95 Final invoice .. .. x
Network/Activities
Milestone Estimate Actual
Assembly 01-03-95 01-03-95
Maintenance 01-04-95
Acceptance 01-05-95
For each billing date in a milestone billing plan, you can specify whether the billing
date is:
1. fixed
2. always updated with the actual date of the milestone
3. updated with the actual date of the milestone, if the date is earlier than the
planned billing date for the date
Reward points if helpful.
Thanks,
T.Nishanth,

Billing plan and billing status

Hello Friends,
I would like to clarify if my understanding is correct before I configure a billing plan:
1. Billing status is not seen in billing doc but in preceding doc like a DO.
2. For a Billing Plan, there can be 1 billing plan at item level for a set of settlement dates.
If the plan is defined at header level, only 1 billing plan is for all items.
3. Contract is a sales doc type and contract data is only at header level.
Is this considered an Order-related billing when invoice is printed at each billing date?
Is the contract considered as the reference doc for the billing doc sent to customer? I believe so. please confirm.
4. There is no such thing as master billing plan that item level billing plans need to be linked to.
5. date category : this is at billing date level and cannot be changed?
regards
Pascal

Hello,
Milestone billing means distributing the total amount to be billed over multiple billing
dates in the billing plan.
As each milestone is successfully reached, the customer is billed either a percentage of
the entire project cost or simply a pre-defined amount.
During sales order processing, the system determines from the item category whether a
billing plan is required and, if so, which type of plan
The type of billing plan that is determined at this point is set up in Customizing and
cannot be changed in the sales document.
Billing plans for periodic billing and milestone billing plans for project-related milestone
billing have different overview screens so that you can enter data relevant to your
processing.
For example, for milestone billing, you must be able to enter data to identify the
individual milestones.
Thanks,
venkataswamy.y
IMG configuration requires :-
1. Maintain billing plan types for milestone billing in OVBO.
2. Define date description in SM30 - V_TVTB.
3. Maintain Date Category for Billing Plan Type IN OVBJ.
4. Allocate date category in SM30 - V_TFPLA_TY.
5. Maintain date proposal for Billing Plan Type in OVBM.
6. Assign Billing Plan Type to Sales Documents Type in OVBP.
7. Assign Billing Plan Type to Item Categories in OVBR.
8. Define rules for determining the date in OVBS.
Milestone billing is typically used for billing projects, such as plant engineering and
construction projects. Such projects often include a series of milestones that mark the
completion of different stages of the work. In the SAP R/3 System, milestones are defined
in a network along with planned and actual dates for the completion of work. The milestones
are also assigned to the billing dates in the billing plan.
Each milestone-related billing date is blocked for processing until the Project System
confirms that the milestone is completed.
Delivery-relevant order items for which a milestone billing plan applies are billed on the
basis of the requested delivery quantity and not on the total of the confirmed quantities.
The connection between the project and the sales document item is made in the individual
schedule lines of the item. Each schedule item can be assigned to a network in a project.
To display the project-related data for a schedule line, proceed as follows:
In one of the overview screens of the sales document, select
1. Item -> Schedule lines.
2. Mark the schedule line and select Procurement details.
The following figure shows an example of milestone billing where only the Contract have
been billed :
Order Item Turbine 100,000
Billing Plan
Billing date Description % Value Billing Block Milestone Billing Status
01-10-94 Contract 10 10,000 - x x
01-03-95 Assembly 30 30,000 x x
01-04-95 Maintenance 30 30,000 x x
01-05-95 Acceptance 30 30,000 x x
01-06-95 Final invoice .. .. x
Network/Activities
Milestone Estimate Actual
Assembly 01-03-95 01-03-95
Maintenance 01-04-95
Acceptance 01-05-95
For each billing date in a milestone billing plan, you can specify whether the billing
date is:
1. fixed
2. always updated with the actual date of the milestone
3. updated with the actual date of the milestone, if the date is earlier than the
planned billing date for the date
Comments
the article was great it explained about billng milestone very well

Billing plan value with reference to start & End date

Hi Experts,
Request your earliest support for the achieving the below requirement.
Scenario:We have Billing plan set up for the all contracts - valid for one year.Monthly rental amount for each contract item is maintained as base price for the contract. When the billing plans starts in the middle of the month then, the billing value need to be calculated only for the relevant no of days in 'settlement' and 'To' date of billing plan. How to achieve this?
Net value of the contract item
Net value of the item   102.00 GBP
Tax for the item         15.30
Net value of billing plan for the contract item                                                                                .
Item Net value 408.00                GBP
Billing plan and contract validity details for contract item
Billing Plan Type - PM- Monthly in Advance                                    51- Monthly on First of
Contract Start date       07/15/2009 (02)-Contract Start Date        Billing plan Dates from 07/16/2009 02
Contract plan End date 10/14/2009 (09)-Contract End Date          Billing plan Dates until 10/14/2009 09
Horizon -                                                                                Cal-Id - 01
Dates
Settlement       To                      Billing date         Bill.value    Crcy Block BillSt Man. Cor PayT DCat Billing Ty Price cal
   07/16/2009      07/31/2009        08/01/2009         102.00       GBP   FA     A                                   01      ZC           01 -
> This needs to calculated upon net value for 16 days only
   08/01/2009      08/31/2009    09/01/2009              102.00       GBP   FA      A                                 01      ZC            01--->           between 07/16/2009 to 07/31/2009=102/31*16 = 52.65
   09/01/2009      09/30/2009   10/01/2009               102.00       GBP   FA      A                               01      ZC            01
   10/01/2009      10/14/2009    11/01/2009              102.00       GBP   FA      A                               01      ZC            01
Please suggest if this can be achieved through Billing plan configuration or any user exit that can be used to resolve the issue.
Thanks,
Priyabrata

as far as I know there is NO such standard report.
you would try to build sap query based on VBAK/VBAP using VBFA checking LIKP/LIPS and VBRK/VBRP...
but you may request abaper for more professional report with MKPF/MSEG and BKPF/BSEG

Billing Plan : Quarterly

Hi
I have a scenario where in i want to have Quarterly Billing plan in contract instead of monthly and billing date could be 1st of 4th month or it could be 30th of 3rd month. I am using standard contract type SC in ECC6.
I have tried defining date rule etc. it is not woring out.
Billing plan should be as follows
01.01.2007 - 31.03.2007
01.04.2007 - 30.06.2007
Please help me to know steps. Suitable answer will certainly be rewarded.
Regards
Kalpesh

Hi,
refer these settings for date det rule, billing plan and assigning to item cat, if need ref H29 billing block
4.1.3     Defining Rules for Determining Dates
Use
In this step, you define rules for determining dates for the billing plan.
Procedure
1.     Access the activity using one of the following navigation options:
Transaction Code     SPRO
IMG Menu     Sales and Distribution  Billing  Billing Plan  Defining Rules for Determining Dates
2.     Choose New Entries.
3.     On the New Entries: Details of Added Entries screen, make the following entries:
Field name
Value     Description
Date det. rule     YH     Quarterly advance
Baseline date     07
Time period     3
Time unit     3
Last of month     A
Calendar ID
Contract Data
1.     Access the activity using one of the following navigation options:
Transaction Code     OVBI
IMG Menu     Sales and Distribution  Billing  Billing Plan  Billing Plan Types  Maintain billing plan types for periodic billing
2.     On the Change View Maintain billing plan types for periodic billing: Overview screen, select the billing plan type S3 and choose   Copy as to create a billing plan type.
3.     On the Change view Maintain Billing Plan Types for Periodic Billing : Data screen, overwrite the following existing entries:
Field name
Value     Description
BillingPlanType     S3  Y1     Periodic quarterly BPHT
Next bill.date     50  YH
In advance     Select
4.     Save your entries and choose Back.
8.     Select the item category WVC and choose   Copy as to create a new item category.
9.     On the Change View Maintain Item Categories: Details of Selected Set screen, make following entries:
Field name      Description     User Action and Values     Note
ItCa          YWVQ
          Service Quarterly HT
Business Data
Billing Plan Type          Y1
Determine Cost          X
Revenue Recognition     Time-related revenue recognition     A
Delimit. Start Date     Proposal based on contract start date     A

Pro forma invoice problems if billing plan is used

Hello experts,
i have a problem again with the billing plan.
To problem now is the pro- forma for following case:
A billing plan is used for the items in the sales order. only at the end when the delivery gets prepared at the end, the pro forma invoice will be created.
The billing relevance for the item category is 'I' - with the billing plan type (a partial billing with % used).
For the proforma the entire value should appear on the Pro forma finally when the manufactured modul passes the customs.
I am struggling with the correct copy control settings.
The already billed values do not appear on the PRO Forma - for the 'real bills' it is ok.While creating the pro forma the related message appears in the log.
Which settings in copy control for the copy control (sales order --> billing type (pro forma) do I need to use if I need to have the entire sales order item value on the pro forma bill.
all helpfull answers are highly appreciated.
Thanks a lot in advance
Kurt

Hi Kurt,
If you are using a billing plan say periodic billing plan; then i dont think you will have a delivery created against it. From the order / contract; it would be a billing document.
If you are planning to use any of the billing plans; then invoices are bound to split based on invoicing dates and the settings of billing plan.
If you are planning to pull all the parts for the purpose of customs then probably you can plant to develop a new output type that would print the details from the billing document (instead of Proforma from delivery). This new output type will be used for "N" number of billing documents against a sales order / contract in order to capture all the part numbers in it. So if you have 3 parts in the order and 6 invoices, then the new output would get triggered 6 times and you will end up with 6 prints.
Making changes to incorpoate billing plan related copy control settings would turn your development / configuration more complex.
I hope i understood your question correctly.
Hope this helps;
Regards,
Syed Nasir

Billing plan type determination based on Variant configuration characterist

Similar Messages

Maybe you are looking for