Change in output of invoices - VF02

[Former Member]

Hello SAP Folks,

Hope you all are doing Good.

Basically I am into FI and here we are facing an issue with billing document print preview/print out.

User has generated two billing documents with same customer (Direct Debit)

One billing document is showing output with Direct Debit Message.

The other billing document is showing output with GIRO Credit Message.

Could you please help me out to identify the root cause of this difference in the output of two invoices.

Early help is appreciated.

Regards,

Gincy.

[Former Member]

Hello Folks,

I am happy to say to i could find out the root cause.

Due to many number or lines in the material description, it was printing another text below.

I could replicate the issue in our DEV system and our abapers are making the code changes for this form setting.

Thanks for all your inputs.

Regards,

Gincy.

[michael_kozlowski]

In table VBRK check the values of field ZLSCH whether they are equal.

[Former Member]

Hello Michael,

Thanks for showing interest in this discussion.

ZLSCH - Payment method field is blank in both the documents in table VBRK.

Will this make any impact.

Please advice.

Regards,

Gincy.

[michael_kozlowski]

Please clarify with you ABAPer the excact condition in the program flow. Without insight in the code it is very difficult to advise.

Maybe the issue is caused by different partner roles or stuff like that.

[Lakshmipathi]

Moved from SAP ERP SD Billing to Output Management

[Former Member]

Hello Veselina and TW,

Thank you so much for your valuable responses.

I have checked both the billing documents initially before raising this discussion, the customer, output type, printer and material are same for both the billing documents.

Here the user is giving output type manually, which is same for both the documents.

Is there any other point which i have to focus on , please suggest!!

Regards,

Gincy.

[VeselinaPeykova]

Hello .

As already suggested - please check the logic implemented in the the smartform.

First determine the smartform name from transaction NACE-> use V3 as application, find the output type name and you will get the smartform name for transmission medium 1 by navigating to processig routines.

After you have the smartform name, check in transaction SMARTFORMS what logic is implemented. The transaction is very intuitive and does not necessarily require deep ABAP knowledge, but in case you are not completely sure that you have found the root cause, you can ask one of your developers to assist you.

[Former Member]

Hello Veselina,

Thanks for your valuable inputs.

I have gone through all that navigation and found the name of the form. Its a Z form for medium 1 in process routines.

when I enter the name of the form in SMARTFORMS transaction, it is not available.

Please advice how do I check the settings of the form.

Regards,

Gincy.

[VeselinaPeykova]

In case you do not find the form in SMARTFORMS transaction, check again - this may be SAPScript (SE71) or PDF form (SFP). You can see which type of form is used from the same configuration screen in NACE.

This issue seems to take a long time to resolve - after 2 weeks without providing resolution on a problem ticket, probably it would be a good idea to ask any of your colleagues with some SD,MM or ABAP knowledge for assistance.

[Former Member]

Hello Veselina,

In case of document: XXXX(Correct one)

When its going inside the routine z_get_pm, with vbdkr-vbeln = 8003038191 ,  W_PAY_METHOD is getting a blank value. Now the control comes back to the Script with w_pay_method =  ‘     ‘ (blank).

Now according to the code, the control goes inside the else part in the routine with VBDKR-KUNRG=108930, here w_pay_method becomes ‘ D ’ and the standard text gets executed correctly.

Now comes the wrong document  YYYY(Wrong one)

As w_pay_method =  ‘       ‘ (Blank value)

BITMAP 'GIRO TEMPLATE' OBJECT GRAPHICS ID BMAP TYPE BMON DPI 300 gets executed instead of standard text  ‘ZESCC_INV_PM’.

Because, it is going into the else part bypassing the standard text and prints

  BITMAP 'GIRO TEMPLATE' OBJECT GRAPHICS ID BMAP TYPE BMON DPI 300  instead of printing the standard text

Above is the response from ABAP Team.

When I tested in Quality. If its payment method 'D" for customer, it is showing direct debit text in the last page of the invoice.

If the customer is not assigned to payment method 'D', it is showing the GIRO text in the last page of the invoice.

In the above two documents, the customer is same payment method 'D' is assigned to it.

This is the entire scenario.

Please advice where do i check or if i have missed anything to resolve the issue.

Regards,

Gincy.

[VeselinaPeykova]

Since I am not familiar with your business scenario, it is hard to determine whether this behaviour is correct or not - you need to explain the current logic to the business user (try not to be too technical) and ask if this is what they really expect.

If yes (not an issue), then you can ask them to close the ticket.

If not (this is an issue), then ask the user what they really need and request the smartform changes from your development department.

It seems that your ABAP colleagues are really willing to help you - so if any part of their explanation is not clear (forum members cannot look at your custom source code), I believe that they are the best people to answer your further questions, what is more - they can also give you some good ideas on the most effective logic to use for the printform if you can explain to them what exactly is the business requirement.

[Former Member]

Hello Veselina,

The logic is simple here...if its payment method 'D' - Direct Debit test should appear in the output of invoice print preview.

If the payment method is blank... GIRO text should appear.

This is the setting of the form and it is appearing successfully in Quality. Abaper has given the same explanation as well.

But, in production system two invoices are created with same customer. one is showing GIRO text and the other is showing Direct DEbit text.

One thing i could observe that, in both the invoices printer setting is different (Header-->output-->communication method).

Will this make any difference. Please advise.

Regards,

Gincy.

[VeselinaPeykova]

Since the printform logic is that simple (no idea since some z-routine was mentioned somewhere in the explanation), then just check the logic of the form in PRD and find out why the behaviour is not as you expected. Your developer can show you how to debug the printform in PRD by yourself (if you have sufficient authorizations) as an alternative approach to reviewing the source code.

If you believe that a different printer results in different printform behaviour, just change the printer and check - does not make much sense to have such coding, but does not hurt to test.

Have you confirmed that all changes from Quality are successfully imported in PRD in the right sequence- this is one of the first things I would normally check.

Have you read the official SAP documentation on printforms, output configuration and processing during these two weeks? If yes, then you would not really need a step-by-step guidance for your investigation anymore.

[Former Member]

Hello Veselina,

The user has tried with all the printer settings, it is showing the same output.

I think this is not the root cause.

I guess I have checked all the points of investigation. I am not sure what did I miss.

Please advice...how to resolve this issue.

Regards,

Gincy.

[former_member182378]

Gincy,

As you are not an SD analyst, we should keep the first level of investigation very simple:

1. Please ask user if s/he manually entered the different output types in each bill

2. What are the differences between these billing documents - billing type, payer etc.

3. Output condition records are stored in NACH table, you can check this, if output types populate automatically in each bill.

TW

added: if can get hold of an SD analyst, this analysis might not take more than 15 minutes

Message was edited by: TW Typewriter

[VeselinaPeykova]

Since you use SD billing - don't you have a SD consultant to handle such kind of issues?

You probably need to explain to the user how important it is to determine to whom to address a question to ensure faster resolution.

You seem to use custom output types, so the chances to get help from the forum are not very high with the amount of information provided.

Have you tried to perform at least some investigation - compare the billing types, postings?

The user who created th billing documents has sufficient authorization to perform part of the investigation by himself - such as go to vf03, check if the output was manually added, check output determination analysis, check if the output condition records are maintained correctly. These could be even different billing types, but we do not know that .

The user is either not well trained (then he should be asked to refer to the user documentation) or is not following the correct procedures - investigate and provide the results from investigation before posting a problem ticket.

What a consultant can check is if these are two diferent output types and a print requirement is used to determine which one is printed - what is the logic implemented there.

If it is the same output type, the consultant can also check the logic in the smartform.

[former_member182378]

Veselina,

interesting point

If it is the same output type, the consultant can also check the logic in the smartform.

TW

[VeselinaPeykova]

Yes, because in the smartform you can set a condition for printing different texts, perform different calculations and even have a different layout based on a specific criteria. The only serious limitation I can think of is the device type.

[former_member182378]

Veselina,

with device type do you refer to the output device (printer) or some setting in SAP?

TW

[VeselinaPeykova]

I meant that for matrix and laser printing we need separate smartforms.

Especially for matrix printers there are a lot of variables to consider when developing printouts - supported formats (LPI,CPI), barcode handling capabilities, codepages, fonts handling etc.

This is why printforms for matrix are developed for a specific model and the developers need to make some adjustments until the printout looks good. They usually request to be supplied with the same printer model and the additional printer software (if they need to install fonts) during the development phase. The setup usually involves both settings in SAP by BASIS and on the printer itself.