RICEFW Functional and Technical

Specification

9548590 LP South America Wave 1 – Chile, Argentina, and Peru

LPSA - CHILE – ARGENTINA - Observation text for EXPO
invoices Contents
SECTION 1. [ LP to complete].................................................................................................3
OVERVIEW............................................................................................................................3
BUSINESS REQUIREMENTS.....................................................................................................3
ASSUMPTIONS.......................................................................................................................3
KEY DECISIONS AND DEPENDENCIES.......................................................................................3
RPA CONSIDERATIONS...........................................................................................................3
SECURITY CONSIDERATIONS..................................................................................................3
DOCUMENT CONTROL.............................................................................................................3
SECTION 2. [ Capgemini to complete].....................................................................................5
TEST SCENARIOS...................................................................................................................5
RELATED CHANGES REQUESTS................................................................................................5
PRODUCTION CUTOVER TASKS................................................................................................5
UPDATE DOCUMENT REPOSITORY............................................................................................6
CONFIGURATION SETTINGS....................................................................................................6
Configuration Settings BEFORE Changes (in DEV Golden client)........................................................................6
Configuration Settings AFTER Changes (in DEV Golden client)...........................................................................6
Create / Change a Report........................................................................................................6
Report Name, Transaction and Report Variant Information:..................................................................................6
Report Data Fields:................................................................................................................................................ 6
Report Calculation and Formula needed:............................................................................................................... 6
Report Selection Parameters:................................................................................................................................ 7
Create / Change a Form..........................................................................................................7
Event that triggers the form.................................................................................................................................... 7
Specify the output medium..................................................................................................................................... 7
List of printers that will be used to print the form.................................................................................................... 7
Other Considerations............................................................................................................................................. 7
List the specific changes needed........................................................................................................................... 7
Attach copy of current SAP form............................................................................................................................ 8
Attach copy of proposed (red-lined) form............................................................................................................... 8
Create / Change an Interface / Conversion Program...................................................................8
Interface File Source.............................................................................................................................................. 8
Interface Input File Type........................................................................................................................................ 8
Interface File Source.............................................................................................................................................. 8
Describe the information needed on the log file and/or audit trail file.....................................................................8

[Ticket number, Description] 1

 Interface Logical Data Mapping............................................................................................................................. 9
Create / Change an Enhancement............................................................................................9
Describe the current process to be changed.......................................................................................................... 9
Describe the proposed new process...................................................................................................................... 9
Technical Specification Details................................................................................................10
Dependencies...................................................................................................................................................... 11
Technical Design / Pseudo-Code......................................................................................................................... 11
Validations / Error Handling / Correction and Recovery.......................................................................................12
Technical Gaps and Constraints..............................................................................................12

File naming convention is: LP RICEFW [Ticket number] [Description]

[Ticket number, Description] 2

 RICEFW Functional & Technical Specification

SECTION 1.
OVERVIEW
(Overview and purpose of document)
LPNA is requesting to add a paragraph to all exportation invoices.

BUSINESS REQUIREMENTS
(Description of business process change. Document Business Process Flow and Key Benefits)

There is a new international regulation that mandates adding a new phrase to all the exportation
related invoices including Credit and debit memos.

ASSUMPTIONS
(Document assumptions made by the team in developing the proposed design)

KEY DECISIONS AND DEPENDENCIES

RPA CONSIDERATIONS
(LP to confirm that existing BOTS will not be impacted by change)
- Link to RPA Repository List

SECURITY CONSIDERATIONS
(New t-codes, adjust authorization roles)

DOCUMENT CONTROL
(Milestones are Creation, Approval and Deliverable completion)

Version Note
Date Author

01/16/23 Damian Spagnul Created

Approved

Deliverable Completed

b
[Ticket number, Description] 3
 RICEFW Functional & Technical Specification

SECTION 2. [ CAPGEMINI TO COMPLETE]

TEST SCENARIOS
(LP and Capgemini list test scenarios before LP approves RICEFW. Scenarios can be listed or link to
test plan in T-Room. PLEASE note Regression Testing Scenarios as well)

User
Description of Scenario Notes performing the
test

Create an expo invoice + Credit memo + debit memo and process it ECD/ECQ – CAP
Scenario 1:
thru IDCP ECQ - LPSA

Scenario 1: Create an expo invoice + Credit memo + debit memo and process it thru IDCP
ECD

ECQ:

b
[Ticket number, Description] 4
 RICEFW Functional & Technical Specification

RELATED CHANGES REQUESTS

(Include ECC Transports, PI transports, manual import of PI or Portal files in correct sequence)
Transport #/
Transport Description Transport Created by
File

PRODUCTION CUTOVER TASKS

(a) List the SAP task needed to activate this business process in the production client
(b) List the Organizational Change Management changes needed to support this new business process
(e.g. ZPARAM entries, SO23 distribution list, Background scheduling, PI or Portal manual changes.
Note any background schedule changes or PI changes need to be updated in the master document)

UPDATE DOCUMENT REPOSITORY

Destination User Full Name Date Uploaded

Solution Manager

CONFIGURATION SETTINGS
Configuration Settings BEFORE Changes (in DEV Golden client)

Configuration Settings AFTER Changes (in DEV Golden client)

CREATE / CHANGE A REPORT

(if HR report, assign authorization group ZHR to the program)

b
[Ticket number, Description] 5
 RICEFW Functional & Technical Specification

Report Name, Transaction and Report Variant Information:

Is there an existing report that is similar (Yes/No)? NO

If so, name of existing report

Name of report variant that the End User uses

Name of the line layout that the End User uses

Report Data Fields:

SAP Table SAP Field Formula/Calculation or Default Value
Report Column Header
Name Name

Report Calculation and Formula needed:

(Describe any calculations that need to be performed to input/output the data. Provide details about the
conditions under which the calculations will be triggered)

Report Selection Parameters:

SAP Table SAP Field Mandatory / Criteria Validation
Parameter Text / Label
Name Name Optional

CREATE / CHANGE A FORM

Event that triggers the form

Specify the output medium

PDF

b
[Ticket number, Description] 6
 RICEFW Functional & Technical Specification

X``

List of printers that will be used to print the form

SAP Printer Name Printer Model / Type Physical Location

LOCL

Other Considerations
A4

List the specific changes needed

Add the following paragraph
These items are subject to export and economic sanctions regulations. Louisiana Pacific takes its obligations
under these laws very seriously, and expects its business partners to do the same.
No transaction, whether an export transaction or internal transfer or sale, may take place in violation of
applicable export and sanctions regulations.

b
[Ticket number, Description] 7
 RICEFW Functional & Technical Specification

Attach copy of current SAP form

b
[Ticket number, Description] 8
 RICEFW Functional & Technical Specification

Attach copy of proposed (red-lined) form

CREATE / CHANGE AN INTERFACE / CONVERSION PROGRAM

(if HR report, assign authorization group ZHR to the program)

Interface File Source

(Will the file reside on the presentation server, application server, etc.)

b
[Ticket number, Description] 9
 RICEFW Functional & Technical Specification

Interface Input File Type

(Will the file type be ASCII, tab delimited, etc.

Interface File Source

Field Type Field Length
Source of SAP Table-Field name to be
Field Description (char, numeric,
Information populated
etc)

Describe the information needed on the log file and/or audit trail file

Interface Logical Data Mapping

(Attach an Excel spreadsheet with the mapping information or include a screen shot)

CREATE / CHANGE AN ENHANCEMENT

Describe the current process to be changed
(Attach or reference the Business Process Change Scope Document)

Describe the proposed new process

(Attach or reference the Business Process Change Scope Document)

b
[Ticket number, Description] 10
 RICEFW Functional & Technical Specification

TECHNICAL SPECIFICATION DETAILS

Baseline Reference
There is a current logic for exportation when the field VBRP- MATKL <> ‘OSBTECH’ we need to add a text
“Controlled sources PEFC - Certificate Number: SAICA-PEFC-COC-1728019”

On top of that we need to add the following paragraph:

These items are subject to export and economic sanctions regulations. Louisiana Pacific takes its obligations
under these laws very seriously, and expects its business partners to do the same.
No transaction, whether an export transaction or internal transfer or sale, may take place in violation of
applicable export and sanctions regulations.

Development Items Technical Identification

(Use this section to identify all SAP objects being developed or enhanced as a result of the Business
Requirement described in the Functional Specification)

Description
Program Name ZR_OTC_A215_INVOICE_EXPO_XML

Program Description

Function Group

Function Module

Interface Type

Inbound Processing
Description
Techniques
Call Transactions

BAPIs

BADIS

Function Module

ABAP Method

Table Name Description

b
[Ticket number, Description] 11
 RICEFW Functional & Technical Specification

Table Element Data Elements Data Domain Data Fields Description

Structures/IDOC Name Description Include Structures

Indices Structure Name Description

Search Help Structure Name Description

Dependencies

Technical Design / Pseudo-Code

Validations / Error Handling / Correction and Recovery

b
[Ticket number, Description] 12
 RICEFW Functional & Technical Specification

TECHNICAL GAPS AND CONSTRAINTS

(a) Include email date/time stamp and description of the decision
(b) If the decision was made during a conference call, then include the email date/time stamp of the meeting minutes sent
to the user documenting the decision.

b
[Ticket number, Description] 13