Practitioner Portal - Payment Advice Run Email Functionality To Multiple Party and No Email Error Handling

Technical Specification
Technical Specification i
Payment advice eEmail to Vendor Adaptation of the
SAP Forms and IEE Address
(Sending multiple Emails with Variable Sender and Variable Mail Subject and Mail
body functionality and Handling if no email id maintained)
Document Reference
Version
:
Document Status
:
SAPM-2377
V1.0
:
Draft
Author
Maninder SA
Last Revision Date

Date Created
:
:
2708-JanSEP-20154
2708-JanSEP-20154
Page 1 of 14
Approval
Approved by
Process Team
Lead
Development
Team Lead
Name
Hari Lakkaraju
Maninder SA
Role
SD
consultant
ABAP
Consultant
Signature
Date
Document History
Version
Reason for change
Date
1.0
Draft
2808-JanSEP20154
1.1
1.2
1.3
Page 2 of 14
Table of Contents
1 General Information.................................................................3
2 Description and Purpose........................................................5
3 Assumptions............................................................................5
4 Issues........................................................................................5
5 Technical Solution...................................................................6
6 Selection Screen......................................................................6
6.1 Selection Prototype............................................................6
6.2 Details...................................................................................6
7 Detail Logic Notes...................................................................7
8 Interactive Report Flow...........................................................7
9 ALV Options.............................................................................7
10 Sort Criteria Details...............................................................8
11 Calculations and Page Break related Information.............8
12 Error Handling.......................................................................8
12.1 Error Messages...................................................................8
13 Security Requirements/ Authorization Details...................8
14 Additional Information and attachments............................9
15 Testing....................................................................................9
16 UAT Sign Off.........................................................................11
Page 3 of 14
General Information
Report Title:
Module:
Prepared By:
SD
Maninder SA
Prep
Date:
08JanSEP2014
Business/Functional
Hari Lakkaraju
Analyst:
Functional Area
User
Michael Lanners
Priority:
Prio 4
Complexi
Medium
ty:
Transport Information
Object Identifier
Object Type
Change
Task #
(Program ID,
(Program,
Request #
Layout Set ID, etc) Transaction,
Layout Set)
DR1K909 DR1K909 , Notes
ZDADFR01
151DR1K 15236DR1 0000989043
908817
K908818 00010BFFMSI_EM
AILProgram
DR1K909 DR1K909 Transaction
NA
153
154
Config
DR1K909
T
086
Page 4 of 14
DR1K909
112
DR1K909
113
ZSAMPLE_PROC
ESS_00002040
ZSAMPLE_PROC
ESS_00002050
Page 5 of 14
1 Description and Purpose

REQUIREMENT 1 : ZCMR Label
DR1 Delivery Document - ZCMR_LUX : 31146331
Tcode : VL03n
.In the Red Box below , the requirement is that it should show Echternach (City name) ie.If the
field logic is correctly pointing towards City then this can be achieved if we refer to Table ADRC
for this field instead of SADR
REQUIREMENT 2 : CMRS Label

DR1 Delivery Document - CMRS_LUX_SK : Delivery No : 91014213.The document can be
displayed in the same fashion as above.Select output type CMRS instead.
Output Type : CMRS
Application : V2
Program : /WSW/SPEEDI_SF_FORM015
Form : ZVDELFRAB_CMR_SK
Page 6 of 14
In the highlighted boxes above , the Address of the sales org is being shown ie. Luxembourg
but instead it should show the address of shipping point of delivering plant ie. Slovakia
Kechnec.Check this logic for ZCMR output as well.For those fields highlighted the address
shown should be of delivering plant shipping point and not of sales org.This holds true for both
ZCMR and CMRS labels.Also check if field logic is referencing SADT table then it instead be
changed to fetch address from ADRC table
1. Payment Advise to be sent directly to the supplier, once F110 payment run is done.
2. This is to done for all payment method carried through F110.
3. Initially, it should be done for company code 0001(Luxembourg).Provision of Multiple email
sending functionality.
4. Provision of Variable email Sender
54. A copy to be marked to IEE representation as well.Handling of emails, if Vendor master is
not maintained with an Email ID.
2 Assumptions and Prerequisites.
Page 7 of 14
NASAP Notes 0000988859, 0000989043 and 0001033893 needs to be implemented in the
system.
3 Issues
NA
Issue
#
Date
Raised
Issue Description
Issue Resolution
4 Technical Solution
NA
5 Selection Screen
NA
5.1 Selection Prototype

NA.
5.2 Details
1. For Variable Email sender: Implement SAP Notes 0000988859 (if applicable to
system)0000989043 in the SAP system for Payment Advice (Same can be done for
Dunning and Balance confirmations also Refer note details). This step can be skipped if
SAP system already have certain patch level. SNOTE transaction will imply that.
2. Implement SAP Note 0000989043 in the SAP system using SNOTE transaction.
3. For Multiple email sending: Implement SAP Note, 0001033893 in SAP the SAP
system.
4.
Page 8 of 14
a. Tcode SE11: Add the following fields to a z-append structure to the FINAA structure:
Field name
INTUSER
MAIL_SENSITIVITY
MAIL_IMPORTANCE
MAIL_SEND_PRIO
MAIL_SEND_ADDR
MAIL_STATUS_ATTR
MAIL_BODY_FORMAT
MAIL_BODY_TEXT
MAIL_OUTBOX_LINK
Type
UNAME
SO_OBJ_SNS
SO_OBJ_PRI
SO_SND_PRI
AD_SMTPADR
BCS_STML
TEXTF
TDOBNAME
BOOLE_D
5. Address field in SAP Script form ZVDELFRAB_CMR2 and ZVDELFRAB_CMR_SK now gets
value from ADRC table instead of SADR table.
6. Function ModuleImplement BTE 2040 using Tcode FIBF and assign below function
module: to it:
ZSAMPLE_PROCESS_00002040. In this FM, pass the following values to structure
FINAA (Structure for Correspondence) Refer attachment for test code:
ZSAMPLE_PROCESS
_00002040.txt
c_finaa-nacha
c_finaa-intad
c_finaa-namep
c_finaa-intuser
c_finaa-mail_outbox_link
= 'I'.
= lv_mail.
= 'ZVENDOR_EMAIL'.
= 'TEST_USER'.
= 'X'.
REGUH is the structure passed to this FM and has all data pertaining to Payment run.
Any kind of validations like Company Code, Payment methods can be done using this
structure.
## Z-FM is copy of standard FM SAMPLE_PROCESS_00002040.
## Check if Vendor Master have no email id, send a separate email with error message.
## lv_mail is of type intad which contains multiple email ids concatenated by a space.
## ZVENDOR_EMAIL is SO10 text object type FIKO. This is the Email Body.
## TEST_USER is an active SAP user whose email id needs to be the Sender email id.
Code Logic:
DATA: l_addr1_complete TYPE szadr_addr1_complete,

l_adsmtp_line
TYPE szadr_adsmtp_line,
lv_adrnr
TYPE adrnr,
Page 9 of 14
lv_mail
lv_cc
TYPE finaa-intad,
TYPE string VALUE 'Payables@iee.lu'.
IF i_reguh-rzawe = 'C' OR i_reguh-rzawe = 'T'.

IF i_reguh-zbukr = '0001'.
* default: print payment advice
c_finaa-nacha = '1'.
SELECT SINGLE adrnr FROM lfa1 INTO lv_adrnr WHERE lifnr = i_reguhlifnr.
* check that address number is available
IF NOT lv_adrnr IS INITIAL.
"i_reguh-zadnr IS INITIAL.
*
read complete address of vendor/customer

CALL FUNCTION 'ADDR_GET_COMPLETE'
EXPORTING
addrnumber
= lv_adrnr
IMPORTING
addr1_complete = l_addr1_complete
EXCEPTIONS
OTHERS
= 4.
IF sy-subrc EQ 0.
check that internet address is available

READ TABLE l_addr1_complete-adsmtp_tab INTO l_adsmtp_line INDEX 1.
CONCATENATE l_adsmtp_line-adsmtp-smtp_addr lv_cc
INTO lv_mail SEPARATED BY space.
CONDENSE lv_mail.
IF sy-subrc EQ 0 AND NOT l_adsmtp_line-adsmtp-smtp_addr IS INITIAL.
choose message type 'I'nternet and fill email address

c_finaa-nacha = 'I'.
c_finaa-intad = lv_mail.
c_finaa-namep = 'ZVENDOR_EMAIL'.
c_finaa-intuser = 'AHARDT'."'payables@iee.lu''.
c_finaa-mail_outbox_link = 'X'.
ENDIF.
ENDIF.
ENDIF.
ENDIF.
ENDIF.
7. Implement BTE 2050 using Tcode FIBF and assign below function module to it:
ZSAMPLE_PROCESS_00002050. In this FM, pass the following values to structure
C_ITCPO (Structure for Correspondence) Refer attachment for test code:
ZSAMPLE_PROCESS
_00002050.txt
Page 10 of 14
c_itcpo-tdtitle = lv_title.
8. ## lv_title is the Subject line of the email. (It can contain Date, Vendor etc.).Function
Module: ZSAMPLE_PROCESS_00002050
Code Logic:
DATA lv_date TYPE c LENGTH 10.
DATA lv_title TYPE itcpo-tdtitle.
DATA lv_vend TYPE char6.
DATA lv_lifnr TYPE reguh-lifnr.
IF i_reguh-rzawe = 'C' OR i_reguh-rzawe = 'T'.

IF i_reguh-zbukr = '0001'.
WRITE i_reguh-laufd TO lv_date.
CONCATENATE text-001 lv_date INTO
CONDENSE lv_title.
c_itcpo-tdtitle = lv_title.
ENDIF.
ENDIF.
CLEAR:lv_date,lv_title,lv_lifnr.
6 Detail Logic Notes

Report: ZDADFR01
MOVE adrc-city1 TO sadr-ort01.
7 Interactive Report Flow

NA
8 ALV Options
NA
9 Sort Criteria Details

NA
Page 11 of 14
lv_title
SEPARATED BY space.
10 Calculations and Page Break related Information

NA
11
Error Handling
NA
11.1 Error Messages

Describe the expected error messages for different error conditions.
Error Message
Number
NA
Error Message Text

(70 characters)
Error Conditions
12 Security Requirements/ Authorization Details

NA
13 Additional Information and attachments

Document Name
File location
NA
14 Testing
Tested by user.
Page 12 of 14
Comments
15 UAT Sign Off
Page 13 of 14
Page 14 of 14

Practitioner Portal - Payment Advice Run Email Functionality To Multiple Party and No Email Error Handling

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Practitioner Portal - Payment Advice Run Email Functionality To Multiple Party and No Email Error Handling

Încărcat de

Drepturi de autor:

Formate disponibile

Technical Specification

Last Revision Date

Reason for change

1 Description and Purpose

REQUIREMENT 2 : CMRS Label

2 Assumptions and Prerequisites.

5.1 Selection Prototype

DATA: l_addr1_complete TYPE szadr_addr1_complete,

IF i_reguh-rzawe = 'C' OR i_reguh-rzawe = 'T'.

read complete address of vendor/customer

check that internet address is available

choose message type 'I'nternet and fill email address

IF i_reguh-rzawe = 'C' OR i_reguh-rzawe = 'T'.

6 Detail Logic Notes

7 Interactive Report Flow

9 Sort Criteria Details

10 Calculations and Page Break related Information

11.1 Error Messages

Error Message Text

12 Security Requirements/ Authorization Details

13 Additional Information and attachments

15 UAT Sign Off

S-ar putea să vă placă și