cancel
Showing results for 
Search instead for 
Did you mean: 

Mandatory Condition Types in Pricing and Output Control

Former Member
0 Kudos

I have rather two different questions:

1. I am trying to implement a custom pricing condition type (ZFBP) in such a manner that it should appear in the Pricing Elements in the Sales Order automatically but without an amount (to be entered manually). As far as I think, check boxing it as mandatory and manual only dives you the ERROR that ZFBP is missing, it does not make it appear on the list of Pricing Elements only for the amount to be entered. Can I do it like that?

Furthermore, if I make two custom condition types manual ZFBP and ZBPR, make them BOTH manual and required, the error I think only shows the one occurring later in the step of pricing procedure. Can't I do something to make the error like "Mandatory condition ZFBP and ZBPR missing" rather than "Mandatory condition ZBPR missing".

2. I have done virtually everything to solve the problem of Output (Print Preview from Sales Order) but "Output can not be issued Message no. V1104" but it doesn't seem to be working. Since it is a preview, I am assuming suggestions of the performance assistant to the screen suggestions and I don't understand this one:

Issuing to screen

No output types exist in the document.

The output types in the document have not been assigned to the relevant document type in Customizing for output control.

Apparently, this guy also asked the same question but never got the answer. I have tried everything in the suggestions:

Please help.

Accepted Solutions (1)

Accepted Solutions (1)

jignesh_mehta3
Active Contributor
0 Kudos

Regarding Mandatory condition Type, you can maintain the Condition Record in VK11 for the Condition Type & Maint value as 0.00.

Now in V/06, under "Changes which can be made", there is a box for Manual Entries, maintain A there.

There will make sure that Condition Type will be visible in Sales Order with zero value & then user can enter required value in it.

Regarding Output Type: Assign the Output Procedure to Document Type in IMG - Sales and Distribution - Basic Functions - Output Control - Output Determination - Output Determination Using the Condition Technique - Maintain Output Determination for Sales Documents - Maintain Output Determination Procedure & also check other assignments.

Hope this helps,

Thanks,

Jignesh Mehta

Answers (4)

Answers (4)

Former Member
0 Kudos

Apart from the "Output could not be issued" I managed to solve everything.

Former Member
0 Kudos

Hi Shabie,

Let me try to answer your questions one by one.

1. I am trying to implement a custom pricing condition type (ZFBP) in such a manner that it should appear in the Pricing Elements in the Sales Order automatically but without an amount (to be entered manually). As far as I think, check boxing it as mandatory and manual only dives you the ERROR that ZFBP is missing, it does not make it appear on the list of Pricing Elements only for the amount to be entered. Can I do it like that?

Marking the Manual Tick and Mandatory tick in the pricing procedure will make sure user can enter data manually in the sales order condition tab. And it is mandatory. But you cannot make the condition visible and let user enter only the value. This is NOT POSSIBLE as standard SAP is not supporting to that. In pricing execution, system found there is no valid VK11 record for your condition, there for system simply ignore that condition.That's how pricing works in SAP.

Furthermore, if I make two custom condition types manual ZFBP and ZBPR, make them BOTH manual and required, the error I think only shows the one occurring later in the step of pricing procedure. Can't I do something to make the error like "Mandatory condition ZFBP and ZBPR missing" rather than "Mandatory condition ZBPR missing".

Sorry! Again I have to say you can't do that. It's how SAP has designed that. Pricing conditions are executed based on the step no sequence in the pricing procedure. Therefore system issues messages for each step. You cannot combine all messages and issue one with summary of conditions.

You can check below link on how exactly pricing is working in SAP. I found it very useful to understand condition technique in SAP.

[Conditions Technique in SAP|http://learnsaptips.blogspot.com/2011/09/condition-technique-in-sap-step-by-step.html]

2. I have done virtually everything to solve the problem of Output (Print Preview from Sales Order) but "Output can not be issued Message no. V1104" but it doesn't seem to be working. Since it is a preview, I am assuming suggestions of the performance assistant to the screen suggestions and I don't understand this one:

Based on this it seems like the configuration is not completed for your output type. You can simply check it by using the output analysis functionality in the relevant document. System will give your the output procedure and the output types assigned to it. Check whether you can see your output type in it. If you you have to add it to the respective output determination procedure using transaction NACE.

If you're not familiar with output type configuration, hope this will help you!

[Output type config in SAP|http://learnsaptips.blogspot.com/2010/08/output-determination-in-sap.html]

Hope this helps to solve your problems!

Best regards,

Rahal

Former Member
0 Kudos

Dear Friend,

1. I am trying to implement a custom pricing condition type (ZFBP) in such a manner that it should appear in the Pricing Elements in the Sales Order automatically but without an amount (to be entered manually). As far as I think, check boxing it as mandatory and manual only dives you the ERROR that ZFBP is missing, it does not make it appear on the list of Pricing Elements only for the amount to be entered. Can I do it like that?

for this you can do with Transaction variant and screen variant by using T-code SHD0

Thank you,

Former Member
0 Kudos

Hello,

>> Since you had already made the condition types ZFBP and ZBPR as 'required' by checking the mandatory check box in the pricing procedure, the system will expect a value while processing the sales document type. As you know that the system accesses the condition types sequentailly based on the steps and counters you mentioned in the pricing procedure.

The system access the condition types based on the position, once it comes to ZBPR, the system expects a price since it is been made mandatory, it throws error as it has to process this condition type before proceeding to the another one.

It is the standard behaviour os SAP.

>> Regarding the output, did you maintain the condition type in VV11? Do you have any requirement assigned to the condition type? Go to the output in the sales document, check the processing log, or check the output determination analysis, you will come to know why this condition type has been excluded.

Regards,

SAM

Former Member
0 Kudos

Yeah well you are right about the fact I think, I can not change the standard SAP behavior. I'll have to stick with what's available and I'll suggest the maintenance of better condition records so that minimal manual entry to pricing elements is required.

I have just noticed something. My output for same document type (ZA01) to the same customer yields 2 different results depending on the material I use. Both have same Item Cat. but that is not the issue I think because no Item output procedure has been set.

And I made a stupid mistake and quoted the wrong error for output control. I got past the No output error on my own. This is the error I am receiving: Output Could not be Issued.

The link in my previous post also refers to this problem.

Edited by: shabie on Dec 19, 2011 8:51 AM