Skip to Content
0

Header Output with access sequence having field of Line Item

May 09 at 11:21 AM

37

avatar image
Former Member

Hi All,

I am creating a new order coonfirmation which should be triggered only once with all the material items. I thought of having it as a header output type but the access sequence which will control it will have plant and shipping conditions. Will it work to have it triggered on header with item level fields.? How can we achieve this ??

Also is it possible to allow multiple selection option in VV11 like it is there in most of the SAP screen.

untitled.png (25.8 kB)
10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Best Answer
Phil Cooley May 09 at 12:11 PM
0

Hi

While anything is possible you also need to think about whether it makes sense. From a Header output perspective it is always best to base them on Header condition structure fields, not item specifically as the detail on items could change between the items so then how do you generate your output based on multiple values. e.g. if 2 line items had different plants then what would you do with the output.

I would try and see if there are other fields you can base the output on. So rule of thumb or best practices would be - if it is a Header output then base on Header fields, if it is an Item output then based on mixture of header and item fields. This would be the case whether it is pricing, output, text or any configuration in SD - as a rule!

Thanks

Phil Cooley

Show 7 Share
10 |10000 characters needed characters left characters exceeded
Former Member

The requirement is to Generate the Output only once per Document even if it has multiple line items, and it should contain information of all the line items. Mostly plant and shipping condition will b same for all line item.

0

The items can be included in the output program no problems so that is not an issue but it is more generation of the output that will use the communication structures. I would suggest you use Header only communication fields on the access sequence to generate the output record as you will get timing issues on population of the relevant item fields. That is, obviously the item communication fields are populated AFTER the header communication structure fields have been populated.

0
Former Member

Thanks Phil , would try to convince the user . Also are you aware of my 2nd point. That i think is not possible in standard transaction.

0

The output should only generate once anyway as it is a Header condition. Having said this, you can configure to send when anything changes as well which could mean a message is sent anytime a change is made but again it depends on your business requirements.

The output that is generated can contain all information about the items anyway so this is ok. The point about the plant and shipping condition being the same confirms even more they should not be in the key combination of the header determination fields.

Just provide more information on what type of document you are outputting. From VV11 looks like a sales order confirmation or something?

Thanks

Phil

0
Former Member
Phil Cooley

yes it is a sales order confirmation. Mainly this output type will have Tracking link to track the orders, not all orders are sent via courier, so all orders need not have this output. This will be depending on certain combination like plant shipping point etc.

0

OK. Sounds like you need another indicator to detail that the order will be supplied by a Courier. If customer specific, maybe partner function. Not sure on your scenario but good luck with it.

0
Former Member

Thanks Phil, there is no partner function indicated for courier, the indicator for courier service is mainly the shipping point.

Although i am thinking to create two outputs one at header and one at item , item will not have any checks only the condition records and will have a dummy forms and programs.

The header output will have a routine which will pick all the items for which output is processed successfully(i.e found the records). Lets hope it works as expected.

0