Sunteți pe pagina 1din 4

Group MIS technical specification

Title ROCN - AMQHYW - FBL5N FBL1N FBL3N IN:260523


VCR Number
Project Ref
Project Title
Original Author Jader Silva Date 04/17/2018
MIS Functional
Owner

Change overview (Use this section to describe changes made for each new version.
Details may or may not need adding in the other specification detail sections)
Version Date Author Summary of changes
04/17/201 Valter Show the name, CNPJ and CPF in tcode: FBL1N,
1
8 Miranda FBL3N and FBL5N.

1. Outstanding issues (use this section to give details of any outstanding issues that
may affect the operation or maintenance of the development)
Financial's user needs these information to optimize their analyses.

2. Overview (provide an overview of the processing steps of the development


highlighting any key features)
1 – Key User access FBL1N or FBL3N or FBL5N to generate a list of document.

3. Key SAP objects (List the main SAP objects created for this development, such as
programs, transaction codes and bespoke table. Do not list subsidiary objects such as
screens, message texts and data elements)
Object
Object name Description
type
Show the NAME1, STCD1 and STCD2 at the
ZBTE_INTERFACE_000016
Function transaction FBL1N, FBL3N and FBL5N – change lay
50
out.
Function
ZBFFMSMPL Function Group of ZBTE_INTERFACE_00001650
Group
Append
ZNOMECLIFOR Name1, stcd1 and stcd2 to RAPOS.
Structure
Append
ZNOMECLIFOR1 Name1, stcd1 and stcd2 to RAPOSX.
Structure
RAPOS Structure Append ZNOMECLIFOR was included
RAPOSX Structure Append ZNOMECLIFOR1 was included

JCB Group MIS


Page 1 of 4
VCR number:
VCR title:

4. Input and output (If the development receives input from or sends output to
another SAP or third party system then document the details here. Specify the type
(flat file, .csv, .xml) and the structure and meaning of the contents)
If the details are documented elsewhere then make reference to that documentation
rather than copying the details here.
Input
-
Output
-

5. Non SAP changes


Non SAP developments (give details if any part of this development is external to SAP)
-
Non SAP infrastructure changes (give details if this development required any
changes to the operating environment external to SAP (eg firewall changes))
-

6. Using the development(provide instructions for using the development in order


to assist other functional or technical people needing to test or modify it)
Z table setup (list any Z tables required to use the development along with maintenance
instructions and whether they have a bespoke ZT maintenance transaction

Authorisation checks (details of any authorisation checks that are made by the
program)

Running the development (Describe how to run the development including details of
any parameters (unless these are documented in the functional specification). For
developments that are triggered automatically give details of how to trigger them. Also
describe what should happen when the development has run successfully)
SE11 – append structure ZNOMECLIFOR in RFPOS.

SE11 – append structure ZNOMECLIFOR1 in RFPOSX.

JCB Group MIS


Page 2 of 4
VCR number:
VCR title:

Tcode: FIBF - Business Transaction Events (BTE)

JCB Group MIS


Page 3 of 4
VCR number:
VCR title:

Function Group – SE80 - ZBFFMSMPL

Test data (if possible, give details of how to create or find test data to use with the
development in order to assist maintenance developers)
Ambiente: BED220
Transação: FBL1N, FB3N, FBL5N

Request workbench:
BEDK912471 MIRANDAV 17.04.2018 RECOF – FBL1N e FBL5N with
customor/vendor name and CNPJ/CPF

Request customizing:
BEDK912473 200 MIRANDAV 17.04.2018 RECOF – FBL1N e FBL5N with
customor/vendor name and CNPJ/CPF

JCB Group MIS


Page 4 of 4

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