Error in SAPScript Payment Advice

[ross_goodman]

I have created a copy of the payment advice where I have replaced the include references to two standard texts with new references that are seemingly correctly created via SO10. This is all I have done in the form. When I run the output I get a message to say that "The standard letter texts are missing from the accompanying form". Can anyone throw some light on this for me?

Cheers

[Former Member]

Hai Ross,

Payment advices for vendors

-> have a look on the topics open FI and BTE

-> transactions FIBF, BF24, BF44

-> BTE-process 2040-2060

-> fm SAMPLE_PROCESS_00002040

Also Refer these links...

Regards,

Srikanth.

[vinod_gunaware2]

Hi

There is lot of reason by which that error may occur.

1. whether u r testing it same client. If no,then attach

standard text to request using <b>RSTXTRAN</b> then

use Transaction <b>SCC1</b>

2. Remove include statement and again insert using

<b>SE71->Goto editor of window->insert->symbols-

>standard symbols</b>

Also check language and pragapraph of include.

3.if problem still there then u have to debugg the scripts

using activate debugger.

regards

vinod

[Former Member]

Hello Ross,

Please provide some more details as to in which window/which text and which layout as payment advice exists for different country also.

[Former Member]

Hi i am very new to sd module so please can anyone help me and tell me the step by step procedure regarding "output of standard letter for sales promotion" how to do this

its very urgent,

Regards

Biradar

[Clemenss]

Hi,

for a detailed analysis/solution I'd recommend the following:

Usually the payment advice/payment proiposal can be scheduled and created in the background.

Locate the job, display the step list. Step 3 should be the output media program, here it is RFFOM100. In this step, goto variant.

In a second session, start report RFFOM100 and transfer all field values to the selection screen. This may be somewhat tricky because you have to find out the corresponding fields which aou can verify on the selection screen using F1->technical info.

Then save this a as variant. Now you can create the output repeatedly online. Use SE71-utilities-activate debugger to switch on the sapscript debugger. It pops up after starting RFFOM100. Delete the * in CALL FUNCTION field and accept the settings. The debugger stops at every text include. Using single step you can determine what text is found and what is searched for and, last not least, which form you actually use.

You should use transaction FBZP for customizing the form used and for the texts: Paying company codes, your Company code details, Forms, and then sender details. Here you can enter 4 texts for header (i.e. company logo), footer (company details at page bottom), sender (sender address line printed on top of recipients address) and Signatute (like Kind regards, your company).

Those texts should be created with SO10 in all langueages required and included in a transport task using report RSTXTRAN.

Hope this helps,

Clemens Li

[ross_goodman]

All veryu useful comments and helped me solve my issue, thanks.