0% found this document useful (0 votes)
63 views4 pages

Post-Implementation Steps For SAP Note 3423951

Uploaded by

thiiagorabelo
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
63 views4 pages

Post-Implementation Steps For SAP Note 3423951

Uploaded by

thiiagorabelo
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

SAP SE

SAP Note 3423951 –


Post-Implementation Manual Steps
NT 2019.001 Version 1.62

Version 1.0
Table of Contents
1. Introduction 3
1.1 Purpose 3
1.2 Scope 3

2. UDO Report 3
2.1 Execution of NOTE_3423951 Report 3

3. Document Object 4
3.1 Change NOTAFISCAL 4

Confidential SAP SE, 2024 Page 2


1. Introduction

The Brazilian government has published the NF-e Technical Note 2019.001 Version 1.62
introducing fields. This document guides you through the post-implementation steps that are
necessary to perform changes related to this technical note.
1.1 Purpose
The purpose of this document is to guide you on the implementation steps to create new objects
for the NF-e Technical Note 2019.001 Version 1.62.
1.2 Scope
This document guides you through the steps that you need to follow for the NOTE_3423951 UDO
report.

2. UDO Report
2.1 Execution of NOTE_3423951 Report

Perform the manual steps in each system into which you transport the SAP Note for
implementation.

2.1.1. Since report NOTE_3423951 has been developed to be executed in English


only, we recommend that you log on in English.
2.1.2. Access the ABAP Editor: Initial Screen (SE38) transaction, enter
“NOTE_3423951” in the Program field and click Execute.
2.1.3. Select TESTRUN and execute the report.
2.1.4. Check the Simulation Log and ensure that all the messages have a green traffic
light. If there are any warnings and/or error messages that you cannot solve
yourself, create a customer incident under the corresponding component of
NOTE_3423951.
2.1.5. Go back (choose Back or press F3 on your keyboard), select UPDATE &
ACTIVATE, and execute the report again.
2.1.6. The system prompts you to either activate your objects online or in batch mode.
The online mode is recommended as this enables you to see any activation
issues immediately. Use the batch mode option only if activation in online mode
fails with a time out.
2.1.7. Within the Change Log, the system displays a list of all objects processed.
Ensure that all the displayed messages are warnings or information messages. If
there are any warnings and/or error messages that you cannot solve yourself,
create a customer incident under the corresponding component of
NOTE_3423951. If you have selected to activate the objects in batch mode (see
step 2.1.6), check the activation log of the job as explained in the message text
of the Detailed Log.
2.1.8. Select the node with the last execution log (according to the date and time) and
ensure that there are only information messages (green traffic lights). If there are
any warnings and/or error messages that you cannot solve yourself, create a
customer incident under the corresponding component of NOTE_3423951.
2.1.9. If any inactive objects are detected during the release of your transports, execute
the step 2.1.5 to update and activate again.

Confidential SAP SE, 2024 Page 3


3. Document Object
3.1 Change NOTAFISCAL
3.1.1. Access the Change Document Object (SCDO) transaction.
3.1.2. On the Object field, enter “NOTAFISCAL”.
3.1.3. Click on the change button (the Pencil icon).
3.1.4. Click on Add New Line.
3.1.5. On the new line, under Column table, enter the name “J_1BNFPRSMD_CRDT”.
3.1.6. Mark the Int. Table checkbox.
3.1.7. Click on the Save button.
3.1.8. Click on the Generate button.
3.1.9. In the pop-up window, click on the Function button.
3.1.10. Verify the entries (the fields that are automatically filled are the correct ones).
3.1.11. Check the affected objects by the process.
3.1.12. Activate the object.

Confidential SAP SE, 2024 Page 4

You might also like