Dunning

https://s4hclub.
com/ ©
https://www.youtube.com/@s4hclubforyou ©
F150: Dunning by e-mail
Business Transaction Events - Process Interface - Event 00001040 - customer implementation

for dunning notice via email
## Business Transaction Events: Process Interface - Event 00001040: Customer

Implementation for Dunning Notice via Email
Understanding the Event
Event 00001040 is a specific business transaction event within a process interface. It indicates
that a customer has implemented a process to send dunning notices via email. This event is
likely part of a broader credit and collection process.
Key Components and Considerations
1. Business Transaction: This refers to the specific interaction or activity that is being tracked
or managed. In this case, it's the process of sending dunning notices.
2. Process Interface: A process interface defines the boundaries and interactions between
different systems or processes. It ensures smooth data exchange and coordination.
3. Event 00001040: This is a unique identifier or code assigned to this specific event. It allows
for easy tracking and reference.
4. Customer Implementation: This means that the customer, rather than the system provider,
has configured or developed the process of sending dunning notices via email.
5. Dunning Notice: A dunning notice is a formal reminder sent to a customer who has an
overdue payment. It typically includes details about the outstanding amount, due date, and
potential consequences of non-payment.
Potential Implementation Steps
1. Integration with ERP or CRM: Connect the system that sends dunning notices (e.g., ERP
or CRM) to an email marketing platform or SMTP server.
2. Data Mapping: Ensure that the necessary data fields (customer information, invoice details,
dunning level, etc.) are correctly mapped between the systems.
3. Email Template Creation: Design a professional and informative email template for dunning
notices.
4. Automation Rules: Set up rules to trigger the sending of dunning notices based on specific
criteria (e.g., overdue payment amount, number of days overdue).
5. Testing and Validation: Thoroughly test the process to ensure accurate email delivery and
proper formatting.
@Mickaël QUESNOT
https://www.linkedin.com/in/mickaelquesnot/
1
https://s4hclub.com/ ©
6. Compliance and Legal Considerations: Adhere to relevant laws and regulations regarding
dunning notices, including frequency, content, and privacy requirements.
Benefits of Email Dunning Notices
Efficiency: Automated email delivery can save time and resources compared to manual
processes.
Cost-Effectiveness: Email is generally more cost-effective than traditional methods like postal
mail.
Tracking and Reporting: Email platforms can provide detailed tracking and reporting on open
rates, click-through rates, and delivery failures.
Faster Communication: Emails can be delivered quickly, potentially reducing the time it takes
to collect overdue payments.
By effectively implementing event 00001040, businesses can improve their credit and
collection processes, reduce bad debt, and enhance customer relationships.
Would you like to delve deeper into any specific aspect of this event or process?
Business Transaction Events - Process Interface - Event 00001040 - customer

implementation for sending dunning notice via email
Business Transaction Events - Process Interface
Application Area: FI - Accounts payable and Accounts receivable – Dunning
Application of the process BTE event '00001040' –
This process BTE is useful during a dunning run when a dunning notice needs to be sent to the
customer by the medium of an electronic form (EMAIL).
As a default property, the dunning notice gets printed and is sent to the customer either by
scanning the copy or via 'POST'.
But as an environmental aspect to avoid wastage of paper, this same dunning notice could be
a very beneficial if it is sent by means of electronic form directly after the dunning has been
carried out.
So, to achieve this non-standard functionality we need to enhance the standard process.
@Mickaël QUESNOT
2
As 'OPEN FI' is the best technique for such applications, we implement a BTE as a customer.
Procedure Step-by-Step:
First question - How to find which BTE is useful for this application?
Transaction - FIBF - Environment - Info systems (Processes)
@Mickaël QUESNOT
3
Click on execute,
Select the BTE 00001040 as it deals with the Output device/medium
@Mickaël QUESNOT
4
Read the documentation on how this BTE can be utilized up to its maximum extent for the
particular application area.
SAP provides with sample function module which is a standard one and can be copied to a
function module with customer namespace to enhance the standard.
How does this BTE fulfill our requirement?
@Mickaël QUESNOT
5
@Mickaël QUESNOT
6
The structure highlighted 'FINAA' is the structure used to pass the 'Transmission Medium for
Correspondence' for the SAP to process during a dunning run (In this case).
The structure 'FINAA' consists of two major fields required by us to change the transmission
medium of the SAP script/ Smart form for sending it to the customer which are,
1. 'NACHA' - Transmission Medium for Correspondence.
2. 'INTAD' - Internet address of partner company clerk.
@Mickaël QUESNOT
7
Now, we need to incorporate the code into the customer function module,
@Mickaël QUESNOT
8
@Mickaël QUESNOT
9
Complete the values required to be passed to the fields 'C_FINAA-NACHA' and 'C_FINAA-
INTAD',
DATA LT_PAGINFO TYPE BAPIADPAG OCCURS 0.

DATA LT_MAILINFO TYPE BAPIADSMTP OCCURS 0.
@Mickaël QUESNOT
10
DATA LT_RETURN TYPE BAPIRET2 OCCURS 0.

DATA ST_MAILINFO TYPE BAPIADSMTP.
CALL FUNCTION 'BAPI_BUPA_CENTRAL_GETDETAIL'

EXPORTING
BUSINESSPARTNER = I_KNA1-KUNNR
TABLES
PAGADDRESSDATANONADDRESS = LT_PAGINFO
E_MAILDATANONADDRESS = LT_MAILINFO
RETURN = LT_RETURN.
LOOP AT LT_MAILINFO INTO ST_MAILINFO WHERE E_MAIL NE ' '.

EXIT.
ENDLOOP.
C_FINAA-NACHA = 'I'.
C_FINAA-INTAD = ST_MAILINFO-E_MAIL.
Here, NACHA = 'I' stands for 'Internet' as the medium of transmission.
Default is '1' that is by 'Print out', whereas '2' stands for 'FAX'.
Now, similar to the customer exits as like we create 'Projects - CMOD', we create a 'PRODUCT'
to assign the relevant BTE under it.
Follow path, FIBF (Transaction) - Settings - Products - Customer
@Mickaël QUESNOT
11
Create an entry,
Now, to allow the system to check or process our functionality, we need to assign/register
our 'Z' function module under the product (say) 'ZCNAS'.
@Mickaël QUESNOT
12
Observe the entry of the BTE 00001040 registered under the customer product,
Now, technically the BTE is ready to work as we have registered the BTE.
As a functional aspect, two things are needed to be taken care of,
1. Standard communication option - to 'EMAIL' in the 'General' Tab in customer master BP.
@Mickaël QUESNOT
13
2. Clerks 'Internet addresses' under the 'Correspondence' Tab for 'Company code data'.
@Mickaël QUESNOT
14
@Mickaël QUESNOT
15
After configuring these basic steps, the BTE is complete to trigger for dunning run for this
particular customer.
Dunning Run -
Maintaining parameters for the dunning run,
@Mickaël QUESNOT
16
After saving the parameters, go for 'Individual dunning notice' or 'Schedule',
Fill in the required parameters for the dunning run (Individual dunning notice),
@Mickaël QUESNOT
17
After selecting 'Printout' option, confirm the triggering of our BTE 00001040,
Best way is to check in the debugger,
@Mickaël QUESNOT
18
Now, also confirm/observe our 'Z' function module getting triggered,
@Mickaël QUESNOT
19
Process the next step by confirming the 'Send to mail' dialog,

If 'C_FINAA-INTAD' is left blank the system will pick from the customer master 'Clerks
internet', else it will take from the value 'C_FINAA-INTAD'.
@Mickaël QUESNOT
20
To check transfer of the dunning notice to the respective customers via email, visit the
transaction 'SOST' to confirm the status,
@Mickaël QUESNOT
21
Now to view the particular notice as an 'ATTACHMENT',

Select the entry and click on 'Display',
@Mickaël QUESNOT
22
Click on the 'PDF' icon which represents the dunning notice attachment,
@Mickaël QUESNOT
23
@Mickaël QUESNOT
24

Dunning

Uploaded by

Copyright:

Available Formats

Dunning

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Dunning

Uploaded by

Copyright:

Available Formats

https://s4hclub.

F150: Dunning by e-mail

Business Transaction Events - Process Interface - Event 00001040 - customer implementation

## Business Transaction Events: Process Interface - Event 00001040: Customer

Understanding the Event

Key Components and Considerations

Potential Implementation Steps

Benefits of Email Dunning Notices

Business Transaction Events - Process Interface - Event 00001040 - customer

Business Transaction Events - Process Interface

Application Area: FI - Accounts payable and Accounts receivable – Dunning

Application of the process BTE event '00001040' –

Select the BTE 00001040 as it deals with the Output device/medium

DATA LT_PAGINFO TYPE BAPIADPAG OCCURS 0.

DATA LT_RETURN TYPE BAPIRET2 OCCURS 0.

CALL FUNCTION 'BAPI_BUPA_CENTRAL_GETDETAIL'

LOOP AT LT_MAILINFO INTO ST_MAILINFO WHERE E_MAIL NE ' '.

After saving the parameters, go for 'Individual dunning notice' or 'Schedule',

Now, also confirm/observe our 'Z' function module getting triggered,

Process the next step by confirming the 'Send to mail' dialog,

Now to view the particular notice as an 'ATTACHMENT',

You might also like