SO multiple line items but one line item for SD output document

[Former Member]

Hi All,

Have a requirement and I would like to know the best way to approach this.

Customer enters in details on a sales order as following

Line item 10: Material - $20.00 - Customer Mat No: 001

Line item 20: Initial Charge - $20.00 - Customer Mat No: 001

Line item 30: One time Charge - $20.00 - Customer Mat No: 001

For line items that share the same customer material number the customer would like the SD output document to consolidate the 3 line items into one.

Result would look like:

Line item 10: Material 001 - $60:00

SD output is NAST style.

Please advice how can this be done.

Thanks in advance.

[siva_vasireddy2]

Hi,

since it is an output you can discuss with Abaper where in we can pick the cust mat number as intial field and collect all the subsquent items coming under it.

[Jelena]

Not sure why charges are entered as separate line items vs. pricing conditions or billing plan.

Other than that your answer is a custom form (Smartform or Adobe). But you'd need some kind of criteria that would "link" these 3 items.

[VeselinaPeykova]

Even if there is a valid reason to have these as separate line items and if it is absolutely necessary to send item outputs, I would probably set the charges as sub-items and would cumulate the value in the main item (material) in some statistical condition that can be used for sending the total. Then the output determination part becomes a piece of cake, because you need just a print requirement to check uepos. Of course one needs to develop a custom form to retrieve the data.

Still, it beats me why such item output is needed (if this is really about printing or sending e-mails).

[Former Member]

The idea is that the sales order would show 3 items internally but for the customer this would appear as 1 packaged item. The criteria that links these together is the customer material number.

You mention a custom form. I was looking at modifying RBOSORDER01 program.

[Jelena]

I agree. This is exactly scenario I worked with before - the items were linked by UEPOS and we needed to print only main item for some customers.

It's a bit odd requirement but not as uncommon. Actually there are so many weird requirements the customers have sometimes, it's hard to believe.

[Jelena]

Well, you work at SAP, so I guess you can just do whatever the heck you like...

Replying as to SAP customer - yes, usually it's the print program that needs to take care of preparing the data. Ideally, the form should not have any code at all. However, I believe for SAP customers it's usually more practical to have the form handle it. No one uses standard forms anyway, so you'd have to create a custom one. But it's better to use a standard output program because it's maintained by SAP.

Of course, there are scenarios when it's not beneficial to add code to the form. YMMV.

P.S. RBOSORDER01 is a SAPScript program. Unless you're working with 4.0 it's time everyone got off that SAPScript wagon. I really wish SAP would even stop supporting them right now, forcing the customers to just quit cold turkey. Everyone would be better off in less than a year.

[VeselinaPeykova]

I meant that if I am a customer and I place an order, I would expect to receive a single output per order, not multiple e-mails or printouts for each main item.

Combining items in printouts is not uncommon, but I have done this for header outputs.

[Jelena]

My impression was that OP was asking about header output and my answer was based on that. Perhaps OP could clarify.