Output Type is not triggering

[Former Member]

Hi,

We have created routine in output determination(VOFM) to trigger the output type (for IDoc) when ever Sales Order is created and we have configured correctly. Access Sequence containes KOMKBV1, KOMPBV1, etc.

When I checked in development system, I am getting values in KOMKBV1, KOMPBV1, etc and it is serving my purpose,

But when i tested same in quality system, KOMPBV1 structure is not getting values and this is not serving my purpose ( i.e output type is not triggering) .

Could any one please suggest me why it is happening.

Regards,

Aditya.

[Former Member]

Did you transport to Quality system and execute RV80HGEN afteward?

[Former Member]

Yes i did that...but still not working....but surprizingly the same thing is working in Development....

Please suggest what could be the possible cause?

[brad_bohn]

Run your determination analysis from the output screen. It sounds like a config issue though if you are expecting item level output arnd no values are populated. Does the item category have a procedure assigned?

[Former Member]

The output type is at Header level and all the config. is correct. Access sequence is maintained properly.

FYI in the access sequence 5 fields are from header (KOMKBV1) and 1 field from item (KOMPBV1). In debugging iI have checked the stucture KOMPBV1 is not getting values in Integartion but in development it is working fine

Edited by: Aditya K Ghanaria on Nov 29, 2010 4:29 PM

[Former Member]

Has anyone got any clue on this issue. Please suggest

[Former Member]

check if you routine is assigned by customization in the quality system

did you transport the customization order?

another thing, the report RV80HGEN should be executed in QAS too.

regards, Sebastiá

[Former Member]

all customization are intact and I have ran the report aswell

[brad_bohn]

The output type is at Header level and all the config. is correct. Access sequence is maintained properly

Why would you expect the LINE ITEM structure to be filled for a header output type? You mentioned the line item structure not being filled so it stands to reason that you were discussing a line item output condition type. Why would you use a line item field for a header output type anyway? Have you debugged the core output code to see how it works?

[Former Member]

There is no problem with Access sequence

Below are the fields for the accesss sequence.

Sales document type KOMKBV1 AUART

Sales organization KOMKBV1 VKORG

Distribution channel KOMKBV1 VTWEG

Division KOMKBV1 SPART

Customer group 5 KOMKBV1 KVGR5

Plant KOMPBV1 WERKS

The same is working fine in Developemnt but not in quality.

I went to debugging mode while creating a sales order in both systems for checking where exactly KOMPBV1 is getting cleared.

I could find in

SAPMV45A

MV45AF0B_BELEG_BEARBEITEN_ENDE

FORM BELEG_BEARBEITEN_ENDE

Call function messaging

When the program is going in this..... the value for KOMPBV1 is getting cleared in Quality but the same this is working fine in Development...

Hope this coulld help you in understanding the problem better.

Edited by: Aditya K Ghanaria on Nov 30, 2010 4:13 PM

[brad_bohn]

I understand the problem quite clearly...again, you have a line item field in a header level output access (what you displayed is called an 'access', not an 'access sequence'). That does not make sense. If you have all values the same on an order at the item level and you wish to use that item level value at the header level, then you need to use a header level field in the access. If you require a custom field, then you need to add it to KOMKAZ and fill it using the appropriate exit from RVCOMFZZ.

[Former Member]

Hi,

I don't require custom field , the above mentioned issue is only in Quality. In development this is Access is OK and working fine.

[brad_bohn]

Still, you aren't following the normal, standard approach. It makes absolutely no sense to put a line item field in a header access for a header output type. Surely you can understand that, especially once you transported your config to what should be a cleaner QA system and it didn't work. Now if you still want to figure out the difference, then debug both systems side-by-side - any developer should be able to do that.

[Former Member]

Thanks all for your valuable suggestion.

Found the solution:

The problem was in the Item category the Output procedure was not defined because of which this was happening. And the conclusion the header and item can be used for Output determination provided we maintain the above settings.

Edited by: Aditya K Ghanaria on Dec 2, 2010 6:39 AM

Edited by: Aditya K Ghanaria on Dec 2, 2010 6:39 AM

[Former Member]

Got the solution