Localização Brasil - Serviços

Working with Withholding for the Sale of Services in Brazil
November 2009
Working with Withholding for the Sale of Services in Brazil SKU E19ALC-BRA SER-B 1109 Copyright 2009, Oracle and/or its affiliates. All rights reserved.
Trademark Notice Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. License Restrictions Warranty/Consequential Damages Disclaimer This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. Subject to patent protection under one or more of the following U.S. patents: 5,781,908; 5,828,376; 5,950,010; 5,960,204; 5,987,497; 5,995,972; 5,987,497; and 6,223,345. Other patents pending. Warranty Disclaimer The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. Restricted Rights Notice If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are commercial computer software or commercial technical data pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
Hazardous Applications Notice This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications. Third Party Content, Products, and Services Disclaimer This software and documentation may provide access to or information on content, products and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third party content, products and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third party content, products or services.
Contains GNU libgmp library; Copyright 1991 Free Software Foundation, Inc. This library is free software which can be modified and redistributed under the terms of the GNU Library General Public License. Includes Adobe PDF Library, Copyright 1993-2001 Adobe Systems, Inc. and DL Interface, Copyright 1999-2008 Datalogics Inc. All rights reserved. Adobe is a trademark of Adobe Systems Incorporated. Portions of this program contain information proprietary to Microsoft Corporation. Copyright 1985-1999 Microsoft Corporation. Portions of this program contain information proprietary to Tenberry Software, Inc. Copyright 1992-1995 Tenberry Software, Inc. Portions of this program contain information proprietary to Premia Corporation. Copyright 1993 Premia Corporation. This product includes code licensed from RSA Data Security. All rights reserved. This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/). This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com). All rights reserved. This product includes the Sentry Spelling-Checker Engine, Copyright 1993 Wintertree Software Inc. All rights reserved. Open Source Disclosure Oracle takes no responsibility for its use or distribution of any open source or shareware software or documentation and disclaims any and all liability or damages resulting from use of said software or documentation. The following open source software may be used in Oracles JD Edwards EnterpriseOne products and the following disclaimers are provided: This product includes software developed by the Apache Software Foundation (http://www.apache.org/). Copyright (c) 1999-2000 The Apache Software Foundation. All rights reserved. THIS SOFTWARE IS PROVIDED AS IS AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Contents
General Preface About This Documentation Preface .............................................................. .. .. ... ..ix JD Edwards EnterpriseOne Application Prerequisites..................................................... . . . . . . . . .ix Application Fundamentals..................................................................................... . . . . . . . . .ix Documentation Updates and Downloading Documentation.............................................. ..........x Obtaining Documentation Updates.................................................................................x Downloading Documentation.......................................................................................x Additional Resources.......................................................................................... ..........x Typographical Conventions and Visual Cues............................................................... . . . . . . . . .xi Typographical Conventions................................................................................ . . . . . . . .xi Visual Cues...........................................................................................................xii Country, Region, and Industry Identifiers.........................................................................xii Currency Codes.............................................................................................. . . . . . . .xiii Comments and Suggestions.................................................................................. . . . . . . . .xiii Common Fields Used in Implementation Guides.......................................................... . . . . . . . .xiii
Preface Preface to Working with Withholding for the Sale of Services in Brazil.. . . . . . . . . . . . . . . . .......xvii JD Edwards EnterpriseOne Products........................................................................ . . . . . . .xvii JD Edwards EnterpriseOne Application Fundamentals................................................... . . . . . . .xvii Chapter 1 Getting Started With Withholding for the Sale of Services in Brazil.. .................... ..........1 Integrations for Withholding for the Sale of Services in Brazil............................................ ..........1 Withholding for the Sale of Services in Brazil Implementation Overview... .... ... ... ... ... ... ... ... ... ..........1 JD Edwards EnterpriseOne Brazil Localization Implementation Steps........................................1
Chapter 2 Understanding Withholding for the Sale of Services in Brazil............................. ..........3 Withholding for the Sale of Services in Brazil............................................................... ..........3 Changes to Applications Used to Work with Sales Order and Nota Fiscal Processing. . . . . . . . . . . . . . . ..........6
Copyright 2009, Oracle and/or its affiliates. All rights reserved.
Contents
Chapter 3 Setting Up Your System for Withholding for the Sale of Services in Brazil............. ..........7 Setting Up UDCs for Withholding for the Sale of Services................................................ ..........7 Setting Up Withholding Concepts and ISS Exemptions for the Sale of Services... .. ... .. ... .. ... .. .. ..........7 Understanding Withholding Concepts and ISS Exemptions for the Sale of Services. . . . . . . . . . . . ...........8 Forms Used to Set Up Withholding Concepts and ISS Exemptions for the Sale of Services. . . . ..........9 Setting Up Withholding Concepts..................................................................................9 Specifying Exemptions to ISS Withholding............................................................... . . . . . . .10 Setting Up Minimum Amounts for Withholding for the Sale of Services................................. . . . . . . . .11 Understanding Minimum Amounts for Withholding for the Sale of Services... ..................... . . . . . . . .11 Forms Used to Set Up Minimum Amounts for Withholding........................................... . . . . . . . .11 Setting Up Minimum Amounts for Withholding......................................................... . . . . . . . .11
Chapter 4 Entering Sales Orders with Withholding for Services Sold................................. . . . . . . . .13 Entering Withholding Information in Sales Orders for Services.......................................... . . . . . . . .13 Understanding Withholding Information in Sales Orders for Services. ............................... . . . . . . .13 Prerequisites................................................................................................. . . . . . . .15 Forms Used to Enter Withholding Information for Sales Orders for Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16 Entering Withholding Information for Sales Orders for Services...................................... . . . . . . .16
Chapter 5 Processing Notas Fiscais with Supplier Withholding for Services Sold................. . . . . . . . .19 Generating the Nota Fiscal and Calculating Withholding for Services Sold. .......... ......... ........ . . . . . . . .19 Understanding Validations and Calculations For Withholding......................................... . . . . . . .19 Understanding the Minimum Monthly Basis Amount for PIS, COFINS, and CSLL Withholding . . . . . . . . .21 Understanding Changes to the Reverse/Void Nota Fiscal Program (R76559B). . . . .. . . . . . .. . . . . . . . . . . . . . .24 Prerequisite................................................................................................... . . . . . . .24 Running the Generate Nota Fiscal Program............................................................. . . . . . . .24 Modifying Withholding Amounts and Entering Amounts for Stand-Alone Notas Fiscais.. ............ . . . . . . . .24 Understanding Modifications to Withholding Amounts.................................................. . . . . . . .25 Understanding Withholding Amounts on Stand-Alone Notas Fiscais................................. . . . . . . .25 Prerequisites................................................................................................. . . . . . . .25 Forms Use to Modify Withholding Amounts for Services Sold........................................ . . . . . . . .26 Modifying Withholding Amounts for Services Sold...................................................... . . . . . . .26 Printing the Nota Fiscal Document with Withholding Amounts... ........................................ . . . . . . . .26 Understanding Withholding Amounts on Printed Notas Fiscais...................................... . . . . . . . .27 Setting the Withholding Processing Option for Print Nota Fiscal (R76560B)........................ . . . . . . .27
vi
Contents
Generating the Electronic Nota Fiscal with Withholding Amounts....................................... . . . . . . . .27 Understanding Withholding Amounts in the Electronic Nota Fiscal XML File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27 Running the Nota Fiscal Elec. - Outbound Program (R76B560Z1)................................... . . . . . . .28
Appendix A Additional Fields for Electronic Nota Fiscal XML Header and Detail Elements. . . . . . . . . . . . . . . .29 eoTransaction-detail Heading................................................................................. . . . . . . . .29 NFL-Withholdings............................................................................................ . . . . . . .29
Glossary of JD Edwards EnterpriseOne Terms.........................................................31
Index .............................................................................................................47
vii
Contents
viii
About This Documentation Preface

JD Edwards EnterpriseOne implementation guides provide you with the information that you need to implement and use JD Edwards EnterpriseOne applications from Oracle. This preface discusses: JD Edwards EnterpriseOne application prerequisites. Application fundamentals. Documentation updates and downloading documentation. Additional resources. Typographical conventions and visual cues. Comments and suggestions. Common fields in implementation guides. Note. Implementation guides document only elements, such as fields and check boxes, that require additional explanation. If an element is not documented with the process or task in which it is used, then either it requires no additional explanation or it is documented with common fields for the section, chapter, implementation guide, or product line. Fields that are common to all JD Edwards EnterpriseOne applications are defined in this preface.
JD Edwards EnterpriseOne Application Prerequisites

To benefit fully from the information that is covered in these books, you should have a basic understanding of how to use JD Edwards EnterpriseOne applications. You might also want to complete at least one introductory training course, if applicable. You should be familiar with navigating the system and adding, updating, and deleting information by using JD Edwards EnterpriseOne menus, forms, or windows. You should also be comfortable using the World Wide Web and the Microsoft Windows or Windows NT graphical user interface. These books do not review navigation and other basics. They present the information that you need to use the system and implement your JD Edwards EnterpriseOne applications most effectively.
Application Fundamentals
Each application implementation guide provides implementation and processing information for your JD Edwards EnterpriseOne applications. For some applications, additional, essential information describing the setup and design of your system appears in a companion volume of documentation called the application fundamentals implementation guide. Most product lines have a version of the application fundamentals implementation guide. The preface of each implementation guide identifies the application fundamentals implementation guides that are associated with that implementation guide.
ix
General Preface
The application fundamentals implementation guide consists of important topics that apply to many or all JD Edwards EnterpriseOne applications. Whether you are implementing a single application, some combination of applications within the product line, or the entire product line, you should be familiar with the contents of the appropriate application fundamentals implementation guides. They provide the starting points for fundamental implementation tasks.
Documentation Updates and Downloading Documentation

This section discusses how to: Obtain documentation updates. Download documentation.
Obtaining Documentation Updates

You can find updates and additional documentation for this release, as well as previous releases, on Oracles online support portal, Oracle MetaLink 3. Through the Documentation section of Oracles online support portal, Oracle MetaLink 3, you can download files to add to your Implementation Guides Library. Youll find a variety of useful and timely materials, including updates to the full line of JD Edwards EnterpriseOne documentation that is delivered on your implementation guides CD-ROM. Important! Before you upgrade, you must check Oracles online support portal, My Oracle Support, for updates to the upgrade instructions. Oracle continually posts updates as the upgrade process is refined.
See Also
Oracles online support portal, My Oracle Support: https://support.oracle.com/CSP/ui/flash.html
Downloading Documentation
In addition to the complete line of documentation that is delivered on your implementation guide CD-ROM, Oracle makes JD Edwards EnterpriseOne documentation available to you via Oracles website. You can download PDF versions of JD Edwards EnterpriseOne documentation online via the Oracle Technology Network. Oracle makes these PDF files available online for each major release shortly after the software is shipped. See Oracle Technology Network, http://www.oracle.com/technology/documentation/psftent.html
Additional Resources
Additional resources are located on: https://support.oracle.com/CSP/ui/flash.html
General Preface
Typographical Conventions and Visual Cues

This section discusses: Typographical conventions. Visual cues. Country, region, and industry identifiers. Currency codes.
Typographical Conventions
This table contains the typographical conventions that are used in implementation guides:
Typographical Convention or Visual Cue Bold Description Indicates PeopleCode function names, business function names, event names, system function names, method names, language constructs, and PeopleCode reserved words that must be included literally in the function call. Indicates field values, emphasis, and JD Edwards EnterpriseOne or other book-length publication titles. In PeopleCode syntax, italic items are placeholders for arguments that your program must supply. We also use italics when we refer to words as words or letters as letters, as in the following: Enter the letter O. KEY+KEY Indicates a key combination action. For example, a plus sign (+) between keys means that you must hold down the first key while you press the second key. For ALT+W, hold down the ALT key while you press the W key. Indicates a PeopleCode program or other code example. Indicate chapter titles in cross-references and words that are used differently from their intended meanings. Indicate that the preceding item or series can be repeated any number of times in PeopleCode syntax. Indicate a choice between two options in PeopleCode syntax. Options are separated by a pipe ( | ).
Italics
Monospace font (quotation marks)
. . . (ellipses)
{ } (curly braces)
xi
General Preface
Typographical Convention or Visual Cue [ ] (square brackets) & (ampersand)
Description Indicate optional items in PeopleCode syntax. When placed before a parameter in PeopleCode syntax, an ampersand indicates that the parameter is an already instantiated object. Ampersands also precede all PeopleCode variables.
Visual Cues
Implementation guides contain the following visual cues.
Notes
Notes indicate information that you should pay particular attention to as you work with the JD Edwards EnterpriseOne system. Note. Example of a note. If the note is preceded by Important!, the note is crucial and includes information that concerns what you must do for the system to function properly. Important! Example of an important note.
Warnings
Warnings indicate crucial configuration considerations. Pay close attention to warning messages. Warning! Example of a warning.
Cross-References
Implementation guides provide cross-references either under the heading See Also or on a separate line preceded by the word See. Cross-references lead to other documentation that is pertinent to the immediately preceding documentation.
Country, Region, and Industry Identifiers

Information that applies only to a specific country, region, or industry is preceded by a standard identifier in parentheses. This identifier typically appears at the beginning of a section heading, but it may also appear at the beginning of a note or other text. Example of a country-specific heading: (FRA) Hiring an Employee Example of a region-specific heading: (Latin America) Setting Up Depreciation
Country Identifiers
Countries are identified with the International Organization for Standardization (ISO) country code.
xii
General Preface
Region Identifiers
Regions are identified by the region name. The following region identifiers may appear in implementation guides: Asia Pacific Europe Latin America North America
Industry Identifiers
Industries are identified by the industry name or by an abbreviation for that industry. The following industry identifiers may appear in implementation guides: USF (U.S. Federal) E&G (Education and Government)
Currency Codes
Monetary amounts are identified by the ISO currency code.
Comments and Suggestions

Your comments are important to us. We encourage you to tell us what you like, or what you would like to see changed about implementation guides and other Oracle reference and training materials. Please send your suggestions to your product line documentation manager at Oracle Corporation, 500 Oracle Parkway, Redwood Shores, CA 94065, U.S.A. Or email us at appsdoc@us.oracle.com. While we cannot guarantee to answer every email message, we will pay careful attention to your comments and suggestions.
Common Fields Used in Implementation Guides

Address Book Number Enter a unique number that identifies the master record for the entity. An address book number can be the identifier for a customer, supplier, company, employee, applicant, participant, tenant, location, and so on. Depending on the application, the field on the form might refer to the address book number as the customer number, supplier number, or company number, employee or applicant ID, participant number, and so on. Enter the three-character code to specify the currency that you want to use to view transaction amounts. This code enables you to view the transaction amounts as if they were entered in the specified currency rather than the foreign or domestic currency that was used when the transaction was originally entered.
As If Currency Code
xiii
General Preface
Batch Number
Displays a number that identifies a group of transactions to be processed by the system. On entry forms, you can assign the batch number or the system can assign it through the Next Numbers program (P0002). Enter the date in which a batch is created. If you leave this field blank, the system supplies the system date as the batch date. Displays a code from user-defined code (UDC) table 98/IC that indicates the posting status of a batch. Values are: Blank: Batch is unposted and pending approval. A: The batch is approved for posting, has no errors and is in balance, but has not yet been posted. D: The batch posted successfully. E: The batch is in error. You must correct the batch before it can post. P: The system is in the process of posting the batch. The batch is unavailable until the posting process is complete. If errors occur during the post, the batch status changes to E. U: The batch is temporarily unavailable because someone is working with it, or the batch appears to be in use because a power failure occurred while the batch was open.
Batch Date Batch Status
Branch/Plant
Enter a code that identifies a separate entity as a warehouse location, job, project, work center, branch, or plant in which distribution and manufacturing activities occur. In some systems, this is called a business unit. Enter the alphanumeric code that identifies a separate entity within a business for which you want to track costs. In some systems, this is called a branch/plant. Enter the code that represents a specific category code. Category codes are user-defined codes that you customize to handle the tracking and reporting requirements of your organization. Enter a code that identifies a specific organization, fund, or other reporting entity. The company code must already exist in the F0010 table and must identify a reporting entity that has a complete balance sheet. Enter the three-character code that represents the currency of the transaction. JD Edwards EnterpriseOne provides currency codes that are recognized by the International Organization for Standardization (ISO). The system stores currency codes in the F0013 table. Enter the company number associated with the document. This number, used in conjunction with the document number, document type, and general ledger date, uniquely identifies an original document. If you assign next numbers by company and fiscal year, the system uses the document company to retrieve the correct next number for that company. If two or more original documents have the same document number and document type, you can use the document company to display the document that you want.
Business Unit
Category Code
Company
Currency Code
Document Company
Document Number
Displays a number that identifies the original document, which can be a voucher, invoice, journal entry, or time sheet, and so on. On entry forms, you
xiv
General Preface
can assign the original document number or the system can assign it through the Next Numbers program. Document Type Enter the two-character UDC, from UDC table 00/DT, that identifies the origin and purpose of the transaction, such as a voucher, invoice, journal entry, or time sheet. JD Edwards EnterpriseOne reserves these prefixes for the document types indicated: P: Accounts payable documents. R: Accounts receivable documents. T: Time and pay documents. I: Inventory documents. O: Purchase order documents. S: Sales order documents. Effective Date Enter the date on which an address, item, transaction, or record becomes active. The meaning of this field differs, depending on the program. For example, the effective date can represent any of these dates: The date on which a change of address becomes effective. The date on which a lease becomes effective. The date on which a price becomes effective. The date on which the currency exchange rate becomes effective. The date on which a tax rate becomes effective. Fiscal Period and Fiscal Year G/L Date (general ledger date) Enter a number that identifies the general ledger period and year. For many programs, you can leave these fields blank to use the current fiscal period and year defined in the Company Names & Number program (P0010). Enter the date that identifies the financial period to which a transaction will be posted. The system compares the date that you enter on the transaction to the fiscal date pattern assigned to the company to retrieve the appropriate fiscal period number and year, as well as to perform date validations.
xv
General Preface
xvi
Preface to Working with Withholding for the Sale of Services in Brazil

This preface discusses: JD Edwards EnterpriseOne products. JD Edwards EnterpriseOne application fundamentals.
JD Edwards EnterpriseOne Products

This implementation guide refers to these JD Edwards EnterpriseOne products from Oracle: JD Edwards EnterpriseOne Address Book JD Edwards EnterpriseOne Sales Order Management JD Edwards EnterpriseOne Brazilian Localization
JD Edwards EnterpriseOne Application Fundamentals

Additional, essential information describing the setup and design of your system appears in two companion volumes of documentation called: JD Edwards EnterpriseOne Financial Management Application Fundamentals Implementation Guide JD Edwards EnterpriseOne Country-Specific Setup and Processes for the Americas Implementation Guide
xvii
Preface
xviii
CHAPTER 1
Getting Started With Withholding for the Sale of Services in Brazil

This chapter discusses: Integrations Implementation
Integrations for Withholding for the Sale of Services in Brazil

This implementation guide refers to these JD Edwards EnterpriseOne products from Oracle: JD Edwards EnterpriseOne Address Book JD Edwards EnterpriseOne Sales Order Management JD Edwards EnterpriseOne Brazilian Localization
Withholding for the Sale of Services in Brazil Implementation Overview

This section provides an overview of the steps that are required to implement the ESU for withholding for the sale of services in Brazil. In the planning phase of your implementation, take advantage of all JD Edwards EnterpriseOne sources of information, including the installation guides and troubleshooting information. A complete list of these resources appears in the preface in About This Documentation with information about where to find the most current version of each.
JD Edwards EnterpriseOne Brazil Localization Implementation Steps

Step 1. Set up user-defined codes (UDCs) and next numbers. 2. Set up your system for sales order and nota fiscal processing. Reference The implementation guide for your release of Brazil localizations. The implementation guide for your release of Brazil localizations.
Getting Started With Withholding for the Sale of Services in Brazil
Chapter 1
Step 3. Enter Brazil-specific information for address book records.
Reference The implementation guide for your release of Brazil localizations.
CHAPTER 2
Understanding Withholding for the Sale of Services in Brazil

This chapter provides overviews of: Withholding for the sale of services in Brazil. Changes to applications used to work with sales orders and notas fiscais.
See Also
J.D. Edwards OneWorld and JD Edwards EnterpriseOne ISS Tax Processing for Brazil, My Oracle Support Document ID 705499.1. Understanding How to Cause the System to Calculate ISS on Services Only, My Oracle Support Document ID 761286.1. Understanding Changes to INSS Withholding Calculations in Brazil, My Oracle Support Document ID 755338.1.
Withholding for the Sale of Services in Brazil

When you sell goods and services, you prepare and send to your customers a nota fiscal for the goods or service. The nota fiscal includes information about the transaction, including the taxes applied to the transactions. When you sell services to a customer, you must include lines on the nota fiscal for the supplier withholding taxes that are applied to the services that you sell. These withholding amounts are withheld from the payment that the customer makes to you. The system calculates withholding amounts for these withholding types: Imposto de Renda de Pessoa Jurdicais (IRPJ) Instituto Nacional do Seguro Social (INSS) Imposto sobre Servios (ISS) Programa de Integrao Social (PIS) Contribuio para Financiamento da Seguridade Social (COFINS) Contribuio Social sobre o Lucro Lquido (CSLL) The JD Edwards EnterpriseOne applications that you use to enter sales order and nota fiscal information and to generate notas fiscais are modified to enable you to calculate withholding and include the withholding lines on the nota fiscal that you send to your customer. You can provide the withholding amounts on the service notas fiscais that you generate from the sales order process, and when you create a stand-alone nota fiscal.
Chapter 2
When you enter a sales order for a service that you sell, the system enables you to enter withholding concepts for the sales order. The system uses the concepts to obtain the information needed to calculate the withholding amounts when you generate the nota fiscal. When you print the nota fiscal, the system retrieves the calculated amounts and includes them on the nota fiscal. If you need to modify the nota fiscal or void it, the system accesses the stored withholding information and updates it to include the changes. This process flow shows the existing programs that you use to process notas fiscais, and the new programs and tables that you use when you work with withholding for the sale of services:
Chapter 2
Process flow for Withholding on the Sale of Services
Chapter 2
Changes to Applications Used to Work with Sales Order and Nota Fiscal Processing
Previous releases of software for JD Edwards EnterpriseOne enabled you to calculate supplier withholding for services you acquired using the base software in the JD Edwards EnterpriseOne Accounts Payable system and Brazil-specific software. Applications that you use to work with sales order and nota fiscal processing are modified to enable you to work with supplier withholding when you are the supplier of a service. These applications are modified:
Program Services ISS Exempt (P76B106) Nota Fiscal Maintenance - Brazil (P7610B) Description of Modification Modified to provide a menu access to the program. Modified to add a menu option for the new Nota Fiscal Withholdings program (P76B4220), which enables you to enter and maintain withholdings for a service nota fiscal. The Nota Fiscal Maintenance - Brazil program also launches the Nota Fiscal Withholdings program when you click OK on some of the forms in the Nota Fiscal Maintenance - Brazil program for certain transactions. Stand-Alone Nota Fiscal - Inbound and Outbound (P7611B) Modified to add a menu option for the new Nota Fiscal Withholdings program (P76B4220), which enables you to enter and maintain withholdings for a service nota fiscal. The Stand-Alone Nota Fiscal - Inbound and Outbound program also launches the Nota Fiscal Withholdings program when you click OK on some of the forms in the Stand-Alone Nota Fiscal - Inbound and Outbound program for certain outbound transactions. Sales Order Brazilian Additional Information - Brazil (P4210BR) Generate Nota Fiscal (R76558B) Reverse/Void Nota Fiscal (R76559B) Print Nota Fiscal (R76560B) Modified to call the new program SO Brazil Withholding Additional Info BR (P76B4210) for transaction for the sale of services between two legal entities. Modified to calculate withholding for the sale of services. Modified to update lines accumulated amounts for withholding for unprinted notas fiscais and to delete withholding for generated notas fiscais. Modified to: Print withholding information for the sale of services. Add a processing option that enables you to specify a message to print when the service sold is not subject to withholding. Nota Fiscal Elec. - Outbound (R76B560Z1) Modified to include withholding information in the XML file.
CHAPTER 3
Setting Up Your System for Withholding for the Sale of Services in Brazil
This chapter discusses how to: Set up user-defined codes (UDCs) for withholding for the sale of services. Set up withholding concepts and ISS exemptions for the sale of services. Set up minimum amounts for withholding for the sale of services.
See Also
Chapters about setting up your system for address book records, Brazilian taxes, and supplier withholding in the documentation for your release.
Setting Up UDCs for Withholding for the Sale of Services

Before you set up and process withholding for the sale of services, set up these UDC tables.
Government Entities (76B/GE)

The system uses the values in this UDC table to determine whether a company is a government entity. Withholding for the sale of services does not apply to government entities. Set up this UDC table with the code that you use to identify government entities in the Person/Corporation Code field in the Address Book Revision program.
Transaction Nature Items (76B/TT)

The system uses the values in this UDC table to determine whether a transaction nature code applies to goods or services. You set up values in this UDC table for goods. When you run the Generate Nota Fiscal Brazil program (R76588B), the system uses the values in UDC 76B/TT to determine if a line on a sales order is for goods or services. If the transaction nature code is set up in the 76B/TT UDC table, the system processes the line as the sale of a good, and does not apply ISS withholding. If the transaction nature code does not appear in the 76B/TT UDC table, the system processes the line as the sale of a service and applies ISS withholding.
Setting Up Withholding Concepts and ISS Exemptions for the Sale of Services
This section provides an overview of withholding concepts and ISS exemptions for the sale of services and discusses how to:
Chapter 3
Set up withholding concepts Specify exemptions to ISS withholding.
Understanding Withholding Concepts and ISS Exemptions for the Sale of Services
You use the Withholding Concepts Setup BR program (P76B421) to associate tax type codes with an address book record or item, and to specify whether to calculate withholding for the withholding type. The association with the tax type and the flag to indicate whether to calculate withholding is stored as the withholding concept in the Withholding Concepts Setup table (F76B421). Note. The system enables you to select a tax type code from the Tax Code table (F76B0401). You use the Review A/P Tax Code program (P76B0401) to set up the tax type codes to use for the withholding calculations for the services that you sell. The system saves the records that you set up in the Review A/P Tax Code program to the F76B0401 table. If appropriate values do not exist in the F76B0401 table, set up appropriate codes before you set up the withholding concepts in the Withholding Concepts Setup BR program. You set up ISS tax codes in the Taxes Setup by City & Service program (P76B409). You can set up records for concepts by address book number or by item number; or by both the address book number and item number. At minimum, you must specify either the address book number or the item number. When you enter sales orders, the system uses the values that you set up in the Withholding Concepts Setup BR program as default values for the withholding concepts to associate with the sales order. The system compares the company address book number and the item number from the sales order to the values in the F76B421 table. If a value exists for the combination of the address book number and item number, the system uses that value as a default value for the withholding information to associate with the sales order record. If the system does not find the combination of company address book number and item number in the F76B421 table, it looks for the item number. If it does not find the item number, it looks for the company address book record. If none of these values exist in the F76B421 table, the system does not provide a default value. You must select the option to indicate that a withholding type applies to the record that you set up before the system enables the field in which you enter the tax type code. For example, the INSS Concept field is not enabled unless you first select the INSS Subject to Withh. field. When you run the Generate Nota Fiscal program (R76558B) to calculate the withholding amounts, the system uses the withholding concept that you set up in the Withholding Concepts Setup BR program to access the tax type information that you set up in the Review A/P Tax Code, Address Book Additional Information Brazil, and Services ISS Exempt programs. The records include the percentages that the system uses to calculate withholding amounts.
ISS Exemptions
Some companies might be exempt from paying ISS contributions for specific services in specific cities. You can set up an exempt percentage for a specified city/service combination in the Services ISS Exempt program (P76B106). The system saves the exemption information to the Services ISS Exempt table (F76B106) and uses the information when you calculate ISS for notas fiscais that you send to customers for the services that you sell. The system applies the exemption to each sales order line that has the same city/service combination.
Chapter 3
Forms Used to Set Up Withholding Concepts and ISS Exemptions for the Sale of Services
Form Name Work With Withholding Concepts Setup FormID
W76B421A
Navigation
Usage
SO Withholding Setup Review and select existing (G76B4231), Concepts Setup records. Click Add on the Work With Withholding Concepts Setup form. Specify which withholding taxes apply to a company or item and associate a tax type from the F76B0401 or F76B101 table to the address book record or item number. Specify the exempt percentage for each city and service combination.
Withholding Concepts Setup W76B421B
Work with ISS Exempt Percentages
W76B106A
ISS Withholding Setup (G76B41A), Service ISS Exempt
Setting Up Withholding Concepts

Access the Withholding Concepts Setup form. Address Number Enter the company address book number to which the tax types apply. Leave this field blank to associate only an item number to the withholding type. Note. You can set up the withholding concepts by only the company, by only the item number, or by both the company and item number. Enter values in both the Address Number and Item Number fields to associate the withholding to the combination of the address book and item number. Either the Address Number or Item Number field must be completed. At minimum, you must complete either the Address Number or Item Number field. Item Number Enter the short item number of the service for which the withholding tax applies. Leave this field blank to associate only a company address book record to the withholding type. Note. You can set up the withholding concepts by only the company, by only the item number, or by both the company and item number. Enter values in both the Address Number and Item Number fields to associate the withholding to the combination of the address book and item number. At minimum, you must complete either the Address Number or Item Number field. INSS Concept Enter a tax type code that exists in the F76B0401 table for INSS retention. You set up tax code types in the Review A/P Tax Code program. You must select the INSS Subject to Withh. option before you can enter a value in this field. The system uses the value that you set up as a default value when you enter sales orders for services. Select this option to cause the system to calculate withholding for this tax type when you run the Generate Nota Fiscal program. You must select this option before you can enter a value in the INSS Concept field.
INSS Subject to Withh. (INSS subject to withholding)
Chapter 3
CSLL Concept
Enter a tax type code that exists in the F76B0401 for CSLL retention. You set up tax code types in the Review A/P Tax Code program. You must select the CSLL Subject to Withh. option before you can enter a value in this field. The system uses the value that you set up as a default value when you enter sales orders for services. Select to cause the system to calculate withholding for this tax type when you run the Generate Nota Fiscal program. You must select this option before you can enter a value in the CSLL Concept field. Enter a tax type code that exists in the F76B0401 for IRPJ retention. You set up tax code types in the Review A/P Tax Code program. You must select the IRPJ Subject to Withh. option before you can enter a value in this field. The system uses the value that you set up as a default value when you enter sales orders for services. Select to cause the system to calculate withholding for this tax type when you run the Generate Nota Fiscal program. You must select this option before you can enter a value in the IRPJ Concept field. Enter a tax type code that exists in the F76B0401 for PIS retention. You set up tax code types in the Review A/P Tax Code program. You must select the PIS Subject to Withh. option before you can enter a value in this field. The system uses the value that you set up as a default value when you enter sales orders for services. Select to cause the system to calculate withholding for this tax type when you run the Generate Nota Fiscal program. You must select this option before you can enter a value in the PIS Concept field. Enter a tax type code that exists in the F76B0401 for COFINS retention that exists in the F76B0401 table. You set up tax code types in the Review A/P Tax Code program. You must select the COFINS Subject to Withh. option before you can enter a value in this field. The system uses the value that you set up as a default value when you enter sales orders for services. Select to cause the system to calculate withholding for this tax type when you run the Generate Nota Fiscal program. You must select this option before you can enter a value in the COFINS Concept field. Enter a tax type code for ISS that exists in the Taxes Setup by City and Service table (F76B409). You set up service type codes in the Taxes Setup by City & Service program (P76B409). You must select theISS Subject to Withh. option before you can enter a value in this field. Select to cause the system to calculate withholding for this tax type when you run the Generate Nota Fiscal program. You must select this option before you can enter a value in the Service Type Code field.
CSLL Subject to Withh. (CSLL subject to withholding) IRPJ Concept
IRPJ Subject to Withh. (IRPJ subject to withholding) PIS Concept
PIS Subject to Withh. (PIS subject to withholding) COFINS Concept
COFINS Subject to Withh. (COFINS subject to withholding) Service Type Code
ISS Subject to Withh. (ISS subject to withholding)
Specifying Exemptions to ISS Withholding

Access the Work with ISS Exempt Percentages form. Service Type Code Enter a value from the Service Type Code table (F76B408) to specify the type of service that is fully or partially exempt from ISS withholding.
10
Chapter 3
City Code Exempt Percentage ISS
Enter a value that exists in the Fiscal City Code (76B/FC) UDC table to specify the city for which ISS withholding is exempt. Enter the percentage of the amount of the sales order line that is exempt from ISS withholding. The system applies this percentage to each sales order line that has the service type code and city code specified on this form.
Setting Up Minimum Amounts for Withholding for the Sale of Services

This section provides an overview of minimum amounts for withholding for the sale of services and discusses how to set up minimum amounts for withholding.
Understanding Minimum Amounts for Withholding for the Sale of Services

You do not need to calculate withholding for PIS, COFINS, or CSLL until the total of services sold to a customer within a month exceeds a specified amount. You use the Minimum Amount to Withhold program (P76B422) to set up the minimum amounts on which withholding is calculated for each of these withholding type. The system saves the values that you enter to the Minimum Amount to Withhold table (F76B422) and uses the values when you use the Generate Nota Fiscal program (R76588B) to calculate withholding amounts.
See Also
Processing Notas Fiscais with Supplier Withholding for Services, Generating the Nota Fiscal and Calculating Withholding for Services Sold, Understanding the Minimum Monthly Basis Amount for PIS, COFINS, and CSLL Withholding
Forms Used to Set Up Minimum Amounts for Withholding

Form Name Work With Minimum Amount to Withhold Minimum Amount to Withhold FormID
W76B422A
Navigation SO Withholding Setup (G76B4231), Minimum Amount to Withhold Click Add on the Work With Minimum Amount to Withhold form.
Usage Review and select existing records. Specify the minimum amount and effective date for PIS, COFINS, and CSLL withholding types.
W76B422B
Setting Up Minimum Amounts for Withholding

Access the Minimum Amount to Withhold form. Tax Type Effective Date Enter a value from the Tax Code A/P (76B/TR) UDC table to specify the tax type of the withholding amount. Enter the date on which the withholding minimum amount is effective.
11
Chapter 3
Minimum Amount
Enter the minimum accumulated amount on which the system calculates withholding. The system does not calculate the withholding unless the withholding concept is set up to require withholding and the accumulated amount of sales orders for the services sold to a specific customer in a month exceeds the amount in this field.
12
CHAPTER 4
Entering Sales Orders with Withholding for Services Sold

This chapter discusses how to: Enter withholding information for sales orders for services. Modify withholding information in sales orders.
See Also
Chapters about entering sales order information in the documentation for your release. JD Edwards EnterpriseOne Country-Specific Setup and Processes for the Americas 9.0 Implementation Guide, (BRA) Working With Sales Order Processing for Brazil JD Edwards EnterpriseOne Country-Specific Setup and Processes 8.12 Implementation Guide, (BRA) Working With Sales Order Processing for Brazil PeopleSoft EnterpriseOne Sales Order Management 8.11 SP1 PeopleBook, Entering Sales Orders, (BRA) Entering Additional Sales Order Information for Brazil
Entering Withholding Information in Sales Orders for Services

This section provides an overview of withholding information in sales orders for services and discusses how to enter withholding information for sales orders for services.
See Also
The chapters about entering sales orders in the standard software and entering additional sales order information for Brazil in the documentation for your release.
Understanding Withholding Information in Sales Orders for Services

When you sell services to your customers, you can enter withholding information for the sales order lines for the services. The system uses the withholding concept, service code, and city code that you enter in the sales order when you generate the nota fiscal and calculate the withholding amounts.
13
Chapter 4
You use the SO Brazil Withholding Additional Info program (P76B4210) to enter or modify the withholding information associated with a sales order. If certain conditions exist when you enter a sales order or add lines to an existing sales order, the system launches the forms for the SO Brazil Withholding Additional Info program after you click OK on the S.O. Brazilian Information Detail form. You can also access the forms of the SO Brazil Withholding Additional Info program when you use the Regional Info menu options in the sales order entry process. The system populates the forms in the SO Brazil Withholding Additional Info program with default values that you set up for the withholding concept, service codes, and city code. You can change the values if needed. This table shows the conditions that must exist to enable you to work with withholding for sales orders for services sold:
Condition The sales order line is for a service. The transaction is between two companies. Description The system compares the transaction nature code of the sales order line to the Transaction Nature Items (76B/TT) UDC table. The system runs a validation routine to determine if the selling company and the buying company are legal entities that are not government agencies. The system uses the values in the 76B/GE UDC table to determine if a company is a government agency. The sales order line cannot be at status 999 (closed). Additionally the processing options on the Edit tab in the Nota Fiscal Maintenance Brazil program (P7610B) must be set to enable modifications.
The sales order line is at a status that allows modification.
When you complete the final save function for the sales order, the system saves the withholding information to the Sales Order Withholding Concept Tag File (F76B423).
Default Values
The system displays the forms on which you enter or modify withholding information when certain conditions exist for the transaction. If withholding information was set up in the Withholding Concept Setup program (P76B421), the forms include the default information stored in the Withholding Concept Setup table (F76B421). The system uses this hierarchy to retrieve information from the F76B421 table: 1. Short item number (data item ITM) of the sales order line along with the address number of the legal company. If the system does not find default values for the item number and address number combination, the system goes to the next step of the hierarchy. 2. Short item number of the sales order without using the address number of the legal company. If the system does not find default values for the short item number, the system goes to the next step of the hierarchy. 3. Address book number of the legal company. If the system does not find default values for the legal company, it displays a warning message. You can accept the warning and continue processing the transaction. Default values for the city code, sales service fiscal code, and service national code are not stored in the F76B421 table. The system retrieves default values from these tables: City code
14
Chapter 4
The system retrieves the city code from the address book supplemental data set up in the Supplemental Data table (F00092). Sales service fiscal code The system retrieves the sales service fiscal code from the Service Fiscal Code table (F76B405). Service national code The system retrieves the service national code from the Service Type Code table (F76B408).
Validations
Default and user-entered values in the forms of the SO Brazil Withholding Additional Info program are valid when: Each withholding concept is set up with a valid value from the Tax Code table (F76B0401). Valid values are those that are set up with the correct tax type code from UDC table 76B/TR and are set up as tax codes for retention. For example, a withholding concept for PIS (Programa de Integrao Social) must use a value from the F76B0401 table that has 05 (PIS) in the Tax Type field (data item BRTXTP) and R (retention) in the Retention/Aggregation/Credit field (data item BRRTA). Each withholding concept for which withholding applies includes a valid value. For example, if INSS (Instituto Nacional do Seguro Social) withholding applies, the option to apply INSS must be enabled and a withholding concept for INSS must be entered. If ISS (Imposto sobre Servios) withholding applies: - The value for the city code must be completed with a valid value from UDC table 76B/FC. - The Service Type field must be completed with a valid value from the F76B408 table. The Sales Service Fiscal Code and Service National Code must be populated with valid values. The system automatically populates the Sales Service Fiscal Code and Service National Code fields. You cannot edit these fields; the system retrieves them from the setup for ISS withholding. If the values for these fields are not setup in the Service Fiscal Code program (P76B405) and Service National Codes program (P76B407), the system displays a warning message. See J.D. Edwards OneWorld and JD Edwards EnterpriseOne ISS Tax Processing for Brazil, My Oracle Support document ID 705499.1.
Prerequisites
Before you perform the task in this section: Set up the processing options for the Sales Order Brazilian Additional Information - Brazil program (P4210BR). Verify that withholding concepts are set up appropriately. Verify that ISS withholding setup is complete.
15
Chapter 4
Forms Used to Enter Withholding Information for Sales Orders for Services
Form Name Work With Sales Order Headers Sales Order Header
W4210H
FormID
Navigation Sales Order Processing Brazil (G76B4211), Enter Sales Orders Header Click Add on the Work With Sales Order Headers form. Click OK on the Sales Order Header form.
Usage Review and select sales order header records. Add and revise sales order header information. Add and revise item information in the detail portion of the form. Enter line default information in addition to item information when you do not enter sales order headers.
W4210G
Sales Order Detail Revisions W4210A
Order Acceptance
W42232A
Click OK on the Sales Order Detail Revisions form. Click Place Order on the Order Acceptance form. Click OK on the S.O. Brazilian Additional Information Header form. Click OK on the S.O. Brazilian Information Detail form.
Click the appropriate button to place the order or to revise the order. Add and revise the transaction nature code and transaction nature suffix. Add and revise additional detail information for the Brazilian sales order. Enter or modify withholding information for the sales order line.
S.O. Brazilian Information Header S.O. Brazilian Information Detail SO Brazil Withholding Additional Information
W4210BRL
W4210BRQ
W76B4210A
Entering Withholding Information for Sales Orders for Services

Access the SO Brazil Withholding Additional Information form. The system populates the values on the form based on the values for the item number and legal company address book number. You can modify the withholding concepts and whether to apply the withholding to each line for a service on a sales order. Note. The forms that appear when you use the Regional Info menu options to modify withholding information are slightly different from the form that appears when you add a sales order. IRPJ Withholding Concept([Imposto de Renda de Pessoa Jurdicais] withholding concept) IRPJ Withholding Flag Enter a tax type code for IRPJ that exists in the F76B0401 table. You set up tax code types in the Review A/P Tax Code program. You must select the IRPJ Withholding Flag option before you can enter a value in this field. Select to cause the system to calculate withholding for this tax type when you run the Generate Nota Fiscal program. You must select this option before you can enter a value in the IRPJ Withholding Concept field.
16
Chapter 4
INSS Withholding Concept
Enter a tax type code for INSS that exists in the F76B0401 table. You set up tax code types in the Review A/P Tax Code program. You must select the INSS Withholding Flag option before you can enter a value in this field. Select to cause the system to calculate withholding for this tax type when you run the Generate Nota Fiscal program. You must select this option before you can enter a value in the INSS Withholding Concept field. Enter a tax type code for PIS that exists in the F76B0401 table. You set up tax code types in the Review A/P Tax Code program. You must select the PIS Withholding Flag option before you can enter a value in this field. Select to cause the system to calculate withholding for this tax type when you run the Generate Nota Fiscal program. You must select this option before you can enter a value in the PIS Withholding Concept field. Enter a tax type code for COFINS that exists in the F76B0401 table. You set up tax code types in the Review A/P Tax Code program. You must select the COFINS Withholding Flag option before you can enter a value in this field.
INSS Withholding Flag
PIS Withholding Concept
PIS Withholding Flag
COFINS Withholding Concept ([Contribuio para Financiamento da Seguridade Social] withholding concept) COFINS Withholding Flag
Select to cause the system to calculate withholding for this tax type when you run the Generate Nota Fiscal program. You must select this option before you can enter a value in the COFINS Withholding Concept field. Enter a tax type code for CSLL that exists in the F76B0401 table. You set up tax code types in the Review A/P Tax Code program. You must select the CSLL Withholding Flag. option before you can enter a value in this field.
CSLL Withholding Concept([Contribuio Social sobre o Lucro Lquido] withholding concept) CSLL Withholding Flag
Select to cause the system to calculate withholding for this tax type when you run the Generate Nota Fiscal program. You must select this option before you can enter a value in the CSLL Withholding Concept field. Enter a tax type code for ISS that exists in the F76B0401 table. You set up tax code types in the Review A/P Tax Code program. You must select theISS Withholding Flag option before you can enter a value in this field. Select to cause the system to calculate withholding for this tax type when you run the Generate Nota Fiscal program. You must select this option before you can enter a value in the Service Type Code field. Enter a value from the Fiscal City Code (76B/FC) UDC table to specify the city in which the service was sold. The system retrieves the sales service fiscal code from the Service Fiscal Code table (F76B405). You cannot change the default value on this form. The system retrieves the service national code from the Service Type Code table (F76B408). You cannot change the default value on this form.
Service Type Code
ISS Withholding Flag
City Code Sales Service Fiscal Code Service National Code
17
Chapter 4
18
CHAPTER 5
Processing Notas Fiscais with Supplier Withholding for Services Sold

This chapter discusses how to: Generate the nota fiscal and calculate withholding. Modify withholding amounts and enter withholding information for a stand-alone nota fiscal. Print the nota fiscal document with withholding amounts. Generate the electronic nota fiscal XML file with withholding amounts.
See Also
JD Edwards EnterpriseOne Country-Specific Setup and Processes for the Americas 9.0 Implementation Guide, (BRA) Working With Sales Order Processing for Brazil JD Edwards EnterpriseOne Country-Specific Setup and Processes for the Americas 9.0 Implementation Guide, (BRA) Using Electronic Notas Fiscais JD Edwards EnterpriseOne Country-Specific Setup and Processes 8.12 Implementation Guide, (BRA) Working With Sales Order Processing for Brazil PeopleSoft EnterpriseOne Sales Order Management 8.11 SP1 PeopleBook, (BRA) Processing Sales Orders in Brazil Working with NFe Generation in Brazil,My Oracle Support Document ID 752314.1 Working With Notas Fiscais for the Telephone Industry, My Oracle Support Document ID 705477.1
Generating the Nota Fiscal and Calculating Withholding for Services Sold
This section provides overviews of the validations and calculations for withholding, the minimum monthly basis amount for PIS, COFINS, and CSLL withholding, and changes to the process to reverse or void a nota fiscal; lists a prerequisite; and discusses how to run the Generate Nota Fiscal program (R76588B).
See Also
Setting Processing Options for Generate Nota Fiscal (R76588B) in the documentation for your release.
Understanding Validations and Calculations For Withholding

When you run the Generate Nota Fiscal program to calculate withholding amounts for services sold, the system validates that certain conditions apply and then calculates the withholding amount.
19
Chapter 5
Validations
Before the system calculates withholding amounts, it must validate whether certain conditions are met. This table describes the conditions validated:
Validated Condition The sales order is for a service and includes withholding information. Description The system compares the transaction nature code of the lines on the sales order to the values in UDC 76B/TT. If the transaction nature code does not exist in UDC 76B/TT, then the system processes the sales order as a service sales order. The system accesses the Sales Order Withholding Concept Tag File (F76B423) to determine if withholding information exists for the sales order. If no withholding information exists, the system does not process withholding for the sales order. If withholding information for the sales order exists in the F76B423 table, the system retrieves the withholding concepts from the table and uses the concepts to retrieve the withholding percentage from the tax percentages that you set up for the company in the Review A/P Tax Code program (P76B0401) and the Taxes Setup by City & Service program (P76B409). The minimum amounts for PIS, COFINS, and CSLL withholding are met. If the service sold is subject to withholding for PIS, COFINS, or CSLL, the system: Retrieves the minimum amounts from the Minimum Amounts to Withhold table (F76B422). Retrieves the accumulated amounts for services sold to the customer for the month from the SO Accumulated withholdings by CO and AN8 table (F76B424). If the total of the accumulated amount for the month and the total from the new transactions is not greater than the minimum amount stored in the F76B422 table, then the system does not calculate the withholding amounts. If the total of the accumulated amount and the new transaction amount is greater than the minimum amount, then the system calculates the withholding. Whether or not the total exceeds the minimum amount, the system saves the new accumulated amount to the F76B424 table. See Understanding the Minimum Monthly Basis Amount for PIS,
COFINS, and CSLL Withholding
What percentage of the ISS withholding amount is exempt, as set up in the Services ISS Exempt program (P76B106).
The system retrieves the ISS rate, city, service, and current date, and then calculates the ISS withholding amount. The system then applies the exempt percentage to the calculated amount to determine the actual ISS withholding amount.
Calculations
After validating whether withholding amounts should be calculated, the system calculates the withholding and saves the calculated amount for ISS to the Service Nota Fiscal Withholding Amount by Service table (F76B428) and the calculated amounts for IRRF, INSS, PIS, COFINS, and CSLL to the Service Nota Fiscal Withholding Amounts by Formula table (F76B427). The system reads the values in the F76B427 and F76B428 tables when you modify calculated amounts using the Nota Fiscal Withholdings program (P76B4220) and when you print the nota fiscal. This process flow shows how the system determines whether to calculate withholding and the tables to which it saves the withholding information:
20
Chapter 5
Process Flow for Sales of Services Withholding Calculations
Understanding the Minimum Monthly Basis Amount for PIS, COFINS, and CSLL Withholding
Before it calculates withholding amounts for PIS, COFINS, and CSLL, the system verifies that the accumulated basis amount for all service notas fiscais for a customer within the month exceed the minimum amount that you set up in the Minimum Amount to Withhold program (P76B422). The system first determines the basis amount for the current nota fiscal, adds that amount to the accumulated amount that exists in the SO Accumulated withholdings by CO and AN8 table (F76B424), and then accesses the Minimum Amount to Withhold table (F76B422) to retrieve the minimum amount on which the withholding applies.
21
Chapter 5
Basis Amount
When you save the sales order for the services sold, the system creates a record in the Nota Fiscal Detail Brazil table (F7611B). The system uses that record to determine the basis amount that it uses to determine if the current nota fiscal plus the accumulated nota fiscal amount for the month exceeds the minimum monthly basis amount that you set up on the Minimum Amount to Withhold program. To determine the basis amount, the system adds or subtracts from the value of the service sold the values for each of these items in the sales order record in the F7611B table: Adds IPI (Imposto sobre Produtos Industrializados) tax. Adds ICMS substitution (Imposto sobre Circulao de Mercadorias e Servios Substituto). Adds nota fiscal freight. Adds nota fiscal insurance. Adds nota fiscal financial expenses. Subtracts nota fiscal discount. Subtracts ICMS repasse discount. Subtracts ICMS free port zone discount.
Example of Withholding and Accumulated Amounts

As you process notas fiscais for services sold to a customer within a month, the system saves the accumulated basis amount of the notas fiscais to the SO Accumulated withholdings by CO and AN8 table (F76B424). The system also saves the calculated withholding amounts for each tax type for the month to the F76B424 table. When the accumulated basis amount, including the amount of the current nota fiscal, exceeds the minimum basis amount for the tax type, the system begins calculating withholding amounts for the current and subsequent notas fiscais. The first nota fiscal that causes the minimum basis amount to be exceeded includes the calculated withholding amount for the entire accumulated amount. The system accumulates the amounts by legal company and customer. For example, suppose that: You set up the minimum basis amount for PIS at 10,000 Brazilian reais (BRL). The total of the basis amount for the first three notas fiscais that you process does not exceed 10,000 BRL. The fourth nota fiscal that you process for the month brings the total of the accumulated basis amount to 12,000 BRL. In this example, the system would calculate and include on the fourth nota fiscal a withholding amount for the entire 12,000 BRL. Subsequent notas fiscais would include a withholding amount that is calculated based on the basis amount of that single nota fiscal. If you delete or void a nota fiscal, the system adjusts the tax basis amount and nota fiscal withholding amount in the F76B427 table. This table shows how the accumulated basis amount and withholding amounts are maintained in the F76B427 table for a minimum basis amount of 10,000 BRL:
22
Chapter 5
Nota Fiscal (NF) Number 1 2 3 4 5 6 7
NF Total Amount 1000 1000 2000 8000 1000 1000 1000
PIS Rate 10% 20% 10% 10% 10% 10% 20% 0 0 0
NF Withholding Amount
NF Total Accumulated Amount 1000 2000 4000 12000 13000 14000 15000
NF Withholding Accumulated Amount 0 0 0 1200 1300 1400 3000
1200 100 100 1600 Note. User mistakenly enters 1600 instead of 200.
8 9
1000 1000
20% 10%
200 -1300 Note. User nets -1400 for NF 7 to correct amount and +100 for NF 9.
16000 17000
3200 1900
Delete NF 4, 5, and 6
7000 Note. 10,000 deleted from accumulated amount. Accumulated amount is now below minimum. 6000
500 Note. 1400 deleted from accumulated withholding amount.
Delete NF 2
500 Note. No withholding was calculated for NF 2, so the accumulated amount does not change.
10
1000
10%
7000
500
23
Chapter 5
Nota Fiscal (NF) Number 11 12
NF Total Amount 1000 20000
PIS Rate 10% 10% 0
NF Withholding Amount
NF Total Accumulated Amount 8000 28000
NF Withholding Accumulated Amount 500 3200
2800 Note. 10% of the accumulated amount (28000) is calculated.
Understanding Changes to the Reverse/Void Nota Fiscal Program (R76559B)

You use the Reverse/Void Nota Fiscal program to reverse a nota fiscal before or after printing the nota fiscal, and before you run the Sales Update - Brazil program (R76B803). When you run the Reverse/Void Nota Fiscal program for service notas fiscais that include withholding and are not printed, the system deletes the withholding records for the nota fiscal from the Service Nota Fiscal Withholding Amount by Service (F76B428) and Service Nota Fiscal Withholding Amounts by Formula (F76B427) tables, and updates the accumulated amounts in the SO Accumulated withholdings by CO and AN8 table (F76B424). If the nota fiscal was printed, the system updates the accumulated amounts in the F76B424 table, but does not delete the withholding records from the F76B427 and F76B428 tables because the nota fiscal records must be reported in the fiscal books. Note. You use a different process to void a nota fiscal after you run the Sales Update - Brazil program. Refer to the Processing Sales Order Returns, Reverses, and Cancellations in Brazil section of the documentation for your release for information about voiding notas fiscais after you run the Sales Update Brazil program.
Prerequisite
Before running the Generate Nota Fiscal program, set the processing options for the program. See Setting Processing Options for Nota Fiscal Program (R76558B) in the documentation for your release.
Running the Generate Nota Fiscal Program

Select Sales Order Processing - Brazil (G76B4211), Generate Nota Fiscal.
Modifying Withholding Amounts and Entering Amounts for Stand-Alone Notas Fiscais
This section provides overviews of modifications to withholding amounts and withholding amounts on stand-alone notas fiscais; lists prerequisites; and discusses how to modify withholding amounts for services sold.
24
Chapter 5
Understanding Modifications to Withholding Amounts

After you calculate withholding amounts for notas fiscais for services sold, you can use the Nota Fiscal Withholdings program (P76B4220) to modify the withholding concept, rate, basis, and amount; and whether the nota fiscal line is subject to withholding. You can also use the Nota Fiscal Withholdings program to add withholding information to notas fiscais for which no withholding information exists. You can access the Nota Fiscal Withholdings program from the Nota Fiscal Maintenance program (P7610B) or from the Stand Alone Nota Fiscal program (P7611B). When you access the Nota Fiscal Withholdings program from the Nota Fiscal Maintenance program, the system populates the fields SO Brazil Withholding Additional Info form with the data that was saved to the Service Nota Fiscal Withholding by Formula (F76B427) and Service Nota Fiscal Withholdings by Service (F76B428) tables. The system saves the modified data to these tables when you click OK on the SO Brazil Withholding Additional Info form to save the data. The system also saves modifications to PIS, COFINS, and CSLL amounts to the Service Nota Fiscal Accumulated table (F76B424).
Understanding Withholding Amounts on Stand-Alone Notas Fiscais

You might need to create a nota fiscal that does not affect the accounting processes. The stand-alone nota fiscal is not linked to any other accounting processes. For example, when you generate a stand-alone nota fiscal, it does not affect the general ledger, inventory, purchase order, sales order, accounts payable, or accounts receivable processes. Generate a stand-alone nota fiscal only when you want to print a document that does not affect any other accounting process. Because a stand-alone nota fiscal does not obtain the withholding information from a sales order, you must manually enter the rate, amount, basis, and concept for each withholding type that applies to the nota fiscal. You use the Nota Fiscal Withholdings program (P76B4220) to enter the withholding information. You can access this program when the nota fiscal that you work with includes lines for services sold. When you access the SO Brazil Withholding Additional Info form from the Stand Alone Nota Fiscal program, you can add withholding lines or modify existing lines. When you add lines, the system uses values from the Withholding Concepts Setup table (F76B421) as the default values for the withholding concepts. If you modify an existing records, the system retrieves the existing records from the F76B427 and F76B428 tables. When you save new or existing withholding lines, the system saves the modified values to the F76B427 and F76B428 tables. The system also saves new or modified amounts for PIS, COFINS, and CSLL to the F76B424 table.
Prerequisites
Before you complete the tasks in this section: Set the processing options for the Nota Fiscal Maintenance program. Set the processing options for the Stand Alone Nota Fiscal program.
25
Chapter 5
Forms Use to Modify Withholding Amounts for Services Sold

Form Name Work With Nota Fiscal Headers
W7610BG
FormID
Navigation Sales Order Processing Brazil (G76B4211), Nota Fiscal Inquiry - Header Browse Select a record, and select Header Revision from the Row menu on the Work With Nota Fiscal Headers program.
Usage Review and select nota fiscal records.
Nota Fiscal Header Revision W7610BD
Review nota fiscal information for freight, service tax, merchandise tax.
Nota Fiscal Detail Revision
W7610BE
Select Detail Revision from Review and revise detail the Form menu on the Nota information for the nota Fiscal Header Revision form. fiscal record. Stand-Alone Nota Fiscal - Brazil (G76B4321), Stand Alone Nota Fiscal Outbound Click Add on the Work With Stand Alone Nota Fiscal Detail form. Select Detail Revision from the Row menu on the Outbound Nota Fiscal Header Revision form. Select a record on the Nota Fiscal Detail Revision form and then select Withholding Add Info from the Row menu. Review and select stand-alone outbound nota fiscal records. Add stand-alone notas fiscais for outbound processing. Add and revise details for stand-alone outbound nota fiscal records. Add or modify withholding information for notas fiscais.
Work With Stand Alone Nota Fiscal Detail
W7611BJ
Outbound Nota Fiscal Header Revision Nota Fiscal Detail Revision
W7611BD
W7611BF
SO Brazil Withholding Additional Info
W76B4220A
Modifying Withholding Amounts for Services Sold

Access the SO Brazil Withholding Additional Info form. Refer to the section Entering Sales Orders for Withholding for Services Sold, Entering Withholding Information for Sales Orders for Services for descriptions of the fields on this form.
Printing the Nota Fiscal Document with Withholding Amounts

This section provides an overview of withholding amounts on printed notas fiscais and discusses how to set a new processing option for the Print Nota Fiscal program (R76560B).
26
Chapter 5
Understanding Withholding Amounts on Printed Notas Fiscais

You run the Print Nota Fiscal program (R76560B) to print a document that includes the details of the goods or service sold, including the tax amounts, and withholding amounts for sales transactions that include withholding amounts. When you print a nota fiscal for a sales order that includes lines for withholding, the system accesses the F76B427 and F76B428 tables to obtain this information to print in a withholding section on the nota fiscal: Withholding calculation base amount Withholding calculation percentage Withholding amount Service detail The system groups the withholding by withholding type and percentage. If no withholding applies to the services sold, the system prints the withholding section with no amounts for the tax types. You can enter text in a processing option to print on the nota fiscal if no withholding applies to the services on the nota fiscal.
Setting the Withholding Processing Option for Print Nota Fiscal (R76560B)
This section includes only the new processing option for withholding.
Print
3. Withholding Error Message Enter the text to print on the notas fiscais for services sold to a corporate entity that are not subject to withholding. The system uses the values in the F76B427 and F76B428 tables to determine if the service is subject to withholding.
See Also
Using the Electronic Nota Fiscal Process in Brazil My Oracle Support Document ID: 700583.1. This document includes the processing options for the Print Nota Fiscal program, including the changes to the processing options that were made for the electronic nota fiscal process.
Generating the Electronic Nota Fiscal with Withholding Amounts

This section provides an overview of withholding amounts in the electronic nota fiscal XML file and discusses how to run the Nota Fiscal Elec. - Outbound program (R76B560Z1).
Understanding Withholding Amounts in the Electronic Nota Fiscal XML File

You use the Nota Fiscal Elec. - Outbound program (R76B560Z1) to convert the nota fiscal information generated by the Print Nota Fiscal program to an XML version. When you run the Nota Fiscal Elec. Outbound program, the system includes data for the withholding types and amounts for the sale of services between two corporate entities.
27
Chapter 5
See Appendix: Additional Fields for Electronic Nota Fiscal XML Header and Detail Elements Note. The Nota Fiscal Electronic program generates the XML file, but does not format it in the legally required layout. You must use custom programming or third-party software to format the XML file.
Running the Nota Fiscal Elec. - Outbound Program (R76B560Z1)

Use one of these navigations: Select Brazil Elec Invoice - Process (G76BNF1), Print Nota Fiscal. The system launches the Nota Fiscal Elec. - Outbound program after the nota fiscal print process when you set the processing option in the Print Nota Fiscal program to generate the electronic nota fiscal. Select Brazil Elec Invoice - Process (G76BNF1), Nota Fiscal Elec. - Outbound. You can run the Nota Fiscal Elec. - Outbound program separately from this menu option. You must run the Print Nota Fiscal program before you run the Nota Fiscal Elec. - Outbound program.
28
APPENDIX A
Additional Fields for Electronic Nota Fiscal XML Header and Detail Elements
This appendix list the header and detail elements for withholding for services sold. This appendix is an addendum to the appendix in the document named Using the Electronic Nota Fiscal Process in Brazil, which is available on My Oracle Support, Document ID 700583.1.
eoTransaction-detail Heading
This section of the XML is modified to add this section and subsections after the existing section for NFL-ServiceDescription.
NFL-Withholdings
These subordinate headings appear under the NFL-Withholdings heading: NFLW-IR NFLW-INSS NFLW-PIS NFLW-COFINS NFLW-CSLL NFLW-ISS These sub-headings appear under the subordinate headings for all withholding types except ISS. The system obtains the data for IR, INSS, PIS, COFINS, and CSLL from the Service Nota Fiscal Withholding by Formula table (F76B427): NFLW-Concept NFLW-Percentage NFLW-WithholdingBase NFLW-WithholdingBaseSign NFLW-WithholdingAmountSign NFLW-SubjecttoWithhold These sub-headings appear under the NFLW-ISS subordinate heading. The system obtains the data for ISS from the Service Nota Fiscal Withholdings by Service table (F76B428): NFLW-ISS-ServiceTypeCode
29
Additional Fields for Electronic Nota Fiscal XML Header and Detail Elements
Appendix A
NFLW-ISS_CityCode NFLW-ISS-Percentage NFLW-ISS-WithholdingBase NFLW-ISS-WithholdingBaseSign NFLW-ISS-WithholdingAmount NFLW-ISS-Withholding AmountSign NFLW-ISS-Subject toWithhold NFLW-ISS-ServiceNationalCode NFLW-ISS-SalesServiceFiscalCode
30
Glossary of JD Edwards EnterpriseOne Terms

Accessor Methods/Assessors activity rule add mode Advanced Planning Agent (APAg) alternate currency Java methods to get and set the elements of a value object or other source file. The criteria by which an object progresses from one given point to the next in a flow. A condition of a form that enables users to input data. A JD Edwards EnterpriseOne tool that can be used to extract, transform, and load enterprise data. APAg supports access to data sources in the form of rational databases, flat file format, and other data or message encoding, such as XML. A currency that is different from the domestic currency (when dealing with a domestic-only transaction) or the domestic and foreign currency of a transaction. In JD Edwards EnterpriseOne Financial Management, alternate currency processing enables you to enter receipts and payments in a currency other than the one in which they were issued. Application Server Software that provides the business logic for an application program in a distributed environment. The servers can be Oracle Application Server (OAS) or WebSphere Application Server (WAS). A process that enables you to view currency amounts as if they were entered in a currency different from the domestic and foreign currency of the transaction. A process that is run as of a specific point in time to summarize transactions up to that date. For example, you can run various JD Edwards EnterpriseOne reports as of a specific date to determine balances and amounts of accounts, units, and so on as of that date. A database connection through which all database operations are immediately written to the database. A process in JD Edwards EnterpriseOne Supply Management that contains the same keys that are used in another process. A process of transferring records from a third-party system to JD Edwards EnterpriseOne. In JD Edwards EnterpriseOne Financial Management, batch processing enables you to transfer invoices and vouchers that are entered in a system other than JD Edwards EnterpriseOne to JD Edwards EnterpriseOne Accounts Receivable and JD Edwards EnterpriseOne Accounts Payable, respectively. In addition, you can transfer address book information, including customer and supplier records, to JD Edwards EnterpriseOne. batch server batch-of-one immediate A server that is designated for running batch processing requests. A batch server typically does not contain a database nor does it run interactive applications. A transaction method that enables a client application to perform work on a client workstation, then submit the work all at once to a server application for further processing. As a batch process is running on the server, the client application can continue performing other tasks. See also direct connect and store-and-forward. best practices Non-mandatory guidelines that help the developer make better design decisions.
as if processing as of processing
Auto Commit Transaction back-to-back process batch processing
31
Glossary
BPEL
Abbreviation for Business Process Execution Language, a standard web services orchestration language, which enables you to assemble discrete services into an end-to-end process flow. Abbreviation for Business Process Execution Language Process Manager, a comprehensive infrastructure for creating, deploying, and managing BPEL business processes. Configurable settings in a text file that are used by a build program to generate ANT scripts. ANT is a software tool used for automating build processes. These scripts build published business services. An actor that is responsible for building, mastering, and packaging artifacts. Some build engineers are responsible for building application artifacts, and some are responsible for building foundation artifacts. A WIN32 executable that reads build configuration files and generates an ANT script for building published business services. An actor that determines if and why an EnterpriseOne business service needs to be developed. A named set of user-created, reusable business rules and logs that can be called through event rules. Business functions can run a transaction or a subset of a transaction (check inventory, issue work orders, and so on). Business functions also contain the application programming interfaces (APIs) that enable them to be called from a form, a database trigger, or a non-JD Edwards EnterpriseOne application. Business functions can be combined with other business functions, forms, event rules, and other components to make up an application. Business functions can be created through event rules or third-generation languages, such as C. Examples of business functions include Credit Check and Item Availability. See named event rule (NER). EnterpriseOne business logic written in Java. A business service is a collection of one or more artifacts. Unless specified otherwise, a business service implies both a published business service and business service. Source files, descriptors, and so on that are managed for business service development and are needed for the business service build process. A method that accesses resources provided by the business service framework. Configuration files include, but are not limited to, interop.ini, JDBj.ini, and jdelog.properties. A key and value data pair used during orchestration. Collectively refers to both the code and the key cross reference in the WSG/XPI based system. Utility services installed in a BPEL/ESB environment that are used to access JD Edwards EnterpriseOne orchestration cross-reference data. A framework needed by an integration developer to develop and manage business services. Otherwise known as JDeveloper. A collection of artifacts managed by EnterpriseOne LCM tools. Named and represented within EnterpriseOne LCM similarly to other EnterpriseOne objects like tables, views, forms, and so on.
BPEL PM
Build Configuration File
build engineer
Build Program business analyst business function
business function event rule business service
business service artifacts business service class method business service configuration files business service cross reference business service cross-reference utilities business service development environment business services development tool business service EnterpriseOne object
32
Glossary
business service framework business service payload
Parts of the business service foundation that are specifically for supporting business service development. An object that is passed between an enterprise server and a business services server. The business service payload contains the input to the business service when passed to the business services server. The business service payload contains the results from the business service when passed to the Enterprise Server. In the case of notifications, the return business service payload contains the acknowledgement. Key value data pairs used to control the behavior or functionality of business services. An EnterpriseOne application for developers and administrators to manage business service property records. A classification for business service property at the business service level. This is generally a business service name. A business service level contains one or more business service property groups. Each business service property group may contain zero or more business service property records. A way to categorize business service properties. These properties are categorized by business service. A unique name that identifies the business service property globally in the system. A utility API used in business service development to access EnterpriseOne business service property data. A value for a business service property. A source management system, for example ClearCase, where business service artifacts and build files are stored. Or, a physical directory in network. The physical machine where the business services are located. Business services are run on an application server instance. One type of business service artifact. A text file with the .java file type written to be compiled by a Java compiler. The structural representation of a business service value object used in a C-business function. A utility used to create a business service value object template from a business service value object. The object to be deployed to the business services server. A means for selecting specific columns from one or more JD Edwards EnterpriseOne application tables whose data is used in an application or report. A business view does not select specific rows, nor does it contain any actual data. It is strictly a view through which you can manipulate data. A process that blends a customers modifications to the objects in a current release with objects in a new release. A server that has been designated to contain the originally installed version of the software (central objects) for deployment to client computers. In a typical JD Edwards EnterpriseOne installation, the software is loaded on to one machinethe central server. Then, copies of the software are pushed out or downloaded to various workstations attached to it. That way, if the software is altered or corrupted through its use on workstations, an original set of objects (central objects) is always available on the central server.
business service property Business Service Property Admin Tool business service property business service group
business service property categorization business service property key business service property utilities business service property value business service repository business services server business services source file or business service class business service value object template Business Service Value Object Template Utility business services server artifact business view
central objects merge central server
33
Glossary
charts check-in repository
Tables of information in JD Edwards EnterpriseOne that appear on forms in the software. A repository for developers to check in and check out business service artifacts. There are multiple check-in repositories. Each can be used for a different purpose (for example, development, production, testing, and so on). Component-based interoperability model that enables third-party applications and JD Edwards EnterpriseOne to share logic and data. The JD Edwards EnterpriseOne connector architecture includes Java and COM connectors. A general ledger account in JD Edwards EnterpriseOne Financial Management that is used by the system to offset (balance) journal entries. For example, you can use a contra/clearing account to balance the entries created by allocations in JD Edwards EnterpriseOne Financial Management. An application that, during the Installation Workbench processing, runs the batch applications for the planned merges that update the data dictionary, user-defined codes, menus, and user override tables. A process that blends a customers modifications to the control tables with the data that accompanies a new release. The data used to tie HTTP responses with requests that consist of business service name and method. The process in JD Edwards EnterpriseOne Advanced Cost Accounting of tracing or allocating resources to activities or cost objects. In JD Edwards EnterpriseOne Manufacturing, an element of an items cost (for example, material, labor, or overhead). A valid set of JD Edwards EnterpriseOne username/password/environment/role, EnterpriseOne session, or EnterpriseOne token. Utility services installed in a BPEL/ESB environment that access EnterpriseOne cross-reference data. A logic statement that establishes the relationship between configured item segments. Cross segment edits are used to prevent ordering of configurations that cannot be produced. The process of converting amounts from one currency into another currency, generally for reporting purposes. You can use the currency restatement process, for example, when many currencies must be restated into a single currency for consolidated reporting. A protocol used to facilitate communication between business documents and procurement applications, and between e-commerce hubs and suppliers. A valid database username/password. A server in a local area network that maintains a database and performs searches for client computers. An application that, during the Installation Workbench process, copies all data sources that are defined in the installation plan from the Data Source Master and Table and Data Source Sizing tables in the Planner data source to the system-release number data source. It also updates the Data Source Plan detail record to reflect completion. A calendar that represents the beginning date for the fiscal year and the ending date for each period in that year in standard and 52-period accounting.
connector
contra/clearing account
Control Table Workbench
control tables merge correlation data cost assignment cost component credentials cross-reference utility services cross segment edit
currency restatement
cXML database credentials database server Data Source Workbench
date pattern
34
Glossary
denominated-in currency deployment artifacts deployment server detail information direct connect
The company currency in which financial reports are based. Artifacts that are needed for the deployment process, such as servers, ports, and such. A server that is used to install, maintain, and distribute software to one or more enterprise servers and client workstations. Information that relates to individual lines in JD Edwards EnterpriseOne transactions (for example, voucher pay items and sales order detail lines). A transaction method in which a client application communicates interactively and directly with a server application. See also batch-of-one immediate and store-and-forward.
Do Not Translate (DNT) dual pricing duplicate published business services authorization records embedded application server instance edit code
A type of data source that must exist on the iSeries because of BLOB restrictions. The process of providing prices for goods and services in two currencies. Two published business services authorization records with the same user identification information and published business services identification information. An OC4J instance started by and running wholly within JDeveloper. A code that indicates how a specific value for a report or a form should appear or be formatted. The default edit codes that pertain to reporting require particular attention because they account for a substantial amount of information. A condition of a form that enables users to change data. A method used for formatting and validating user entries against a predefined rule or set of rules. An interoperability model that enables paperless computer-to-computer exchange of business transactions between JD Edwards EnterpriseOne and third-party systems. Companies that use EDI must have translator software to convert data from the EDI standard format to the formats of their computer systems. An event rule that is specific to a particular table or application. Examples include form-to-form calls, hiding a field based on a processing option value, and calling a business function. Contrast with the business function event rule. A central location for sending and receiving all JD Edwards EnterpriseOne messages (system and user generated), regardless of the originating application or user. Each user has a mailbox that contains workflow and other messages, including Active Messages. A server that contains the database and the logic for JD Edwards EnterpriseOne. Middleware infrastructure products or technologies based on web services standards that enable a service-oriented architecture using an event-driven and XML-based messaging framework (the bus). An actor responsible for the EnterpriseOne administration system. A user ID, password, environment, and role used to validate a user of EnterpriseOne. A reusable piece of code that is used to build applications. Object types include tables, forms, business functions, data dictionary items, batch processes, business views, event rules, versions, data structures, and media objects.
edit mode edit rule Electronic Data Interchange (EDI)
embedded event rule
Employee Work Center
enterprise server Enterprise Service Bus (ESB)
EnterpriseOne administrator EnterpriseOne credentials EnterpriseOne object
35
Glossary
EnterpriseOne development client EnterpriseOne extension EnterpriseOne process
Historically called fat client, a collection of installed EnterpriseOne components required to develop EnterpriseOne artifacts, including the Microsoft Windows client and design tools. A JDeveloper component (plug-in) specific to EnterpriseOne. A JDeveloper wizard is a specific example of an extension. A software process that enables JD Edwards EnterpriseOne clients and servers to handle processing requests and run transactions. A client runs one process, and servers can have multiple instances of a process. JD Edwards EnterpriseOne processes can also be dedicated to specific tasks (for example, workflow messages and data replication) to ensure that critical processes dont have to wait if the server is particularly busy. Any EnterpriseOne table, metadata, business function, dictionary information, or other information restricted to authorized users. An application that, during the Installation Workbench process, copies the environment information and Object Configuration Manager tables for each environment from the Planner data source to the system-release number data source. It also updates the Environment Plan detail record to reflect completion. A batch process that monitors pending requests or activities and restarts or forwards them to the next step or user after they have been inactive for a specified amount of time. A logic statement that instructs the system to perform one or more operations based on an activity that can occur in a specific application, such as entering a form or exiting a field. Transaction used by a business service developer to explicitly control the type (auto or manual) and the scope of transaction boundaries within a business service. Published business service source files or parts of published business service source files that are part of the published interface. These are part of the contract with the customer. An entity within a business for which you want to track costs. For example, a facility might be a warehouse location, job, project, work center, or branch/plant. A facility is sometimes referred to as a business unit. A command prompt that enables the user to move quickly among menus and applications by using specific commands. A server that stores files to be accessed by other computers on the network. Unlike a disk server, which appears to the user as a remote disk drive, a file server is a sophisticated device that not only stores files, but also manages them and maintains order as network users request files and make changes to these files. The report processing mode of a processing mode of a program that updates or creates data records. A framework that must be accessible for execution of business services at runtime. This includes, but is not limited to, the Java Connector and JDBj. A server that responds to requests for files via file transfer protocol. Information at the beginning of a table or form. Header information is used to identify or provide control information for the group of records that follows. A generic set of services that are used to do the basic HTTP operations, such as GET, POST, PUT, DELETE, TRACE, HEAD, and OPTIONS with the provided URL.
EnterpriseOne resource Environment Workbench
escalation monitor
event rule
explicit transaction exposed method or value object
facility
fast path file server
final mode foundation FTP server header information HTTP Adapter
36
Glossary
instantiate integration developer
A Java term meaning to create. When a class is instantiated, a new instance is created. The user of the system who develops, runs, and debugs the EnterpriseOne business services. The integration developer uses the EnterpriseOne business services to develop these components. The business logic in previous implementations of EnterpriseOne that exposes a document level interface. This type of logic used to be called XBPs. In EnterpriseOne 8.11, IPs are implemented in Web Services Gateway powered by webMethods. A server that facilitates interaction between diverse operating systems and applications across internal and external networked computer systems. A process used to supplement a companys internal balancing procedures by locating and reporting balancing problems and data inconsistencies. See Z table. Business service source files or parts of business service source files that are not part of the published interface. These could be private or protected methods. These could be value objects not used in published methods. A method for third-party systems to connect to or access JD Edwards EnterpriseOne. In JD Edwards EnterpriseOne, a form-level property which, when enabled, causes the text of application errors to appear on the form. This internet server service resides on the web server and is used to speed up delivery of the Java class files from the database to the client. An alternative data dictionary item description that JD Edwards EnterpriseOne appears based on the product code of the current object. A component-based server that resides in the middle-tier of a server-centric architecture. This server provides middleware services for security and state maintenance, along with data access and persistence. A database driver that enables heterogeneous servers to access each others data. A JD Edwards EnterpriseOne proprietary database middleware package that provides platform-independent APIs, along with client-to-server access. An API used by business functions to invoke other business functions. A JD Edwards EnterpriseOne file (or member for iSeries) that provides the runtime settings required for JD Edwards EnterpriseOne initialization. Specific versions of the file or member must reside on every machine running JD Edwards EnterpriseOne. This includes workstations and servers. Communications programming tools used by server code to regulate access to the same data in multiprocess environments, communicate and coordinate between processes, and create new processes. The main diagnostic log file of JD Edwards EnterpriseOne. This file is always located in the root directory on the primary drive and contains status and error messages from the startup and operation of JD Edwards EnterpriseOne. A JD Edwards EnterpriseOne proprietary communications middleware package. This package is a peer-to-peer, message-based, socket-based, multiprocess communications middleware solution. It handles client-to-server and server-to-server communications for all JD Edwards EnterpriseOne supported platforms. An artifact that JDeveloper uses to categorize and compile source files.
integration point (IP)
integration server integrity test interface table internal method or value object
interoperability model in-your-face-error IServer service jargon Java application server
JDBNET JDEBASE Database Middleware JDECallObject jde.ini
JDEIPC
jde.log
JDENET
JDeveloper Project
37
Glossary
JDeveloper Workspace JMS Queue listener service local repository local standalone BPEL/ESB server Location Workbench
An artifact that JDeveloper uses to organize project files. It contains one or more project files. A Java Messaging service queue used for point-to-point messaging. A listener that listens for XML messages over HTTP. A developers local development environment that is used to store business service artifacts. A standalone BPEL/ESB server that is not installed within an application server. An application that, during the Installation Workbench process, copies all locations that are defined in the installation plan from the Location Master table in the Planner data source to the system data source. A server in a distributed network that provides the business logic for an application program. In a typical configuration, pristine objects are replicated on to the logic server from the central server. The logic server, in conjunction with workstations, actually performs the processing required when JD Edwards EnterpriseOne software runs. An application that merges Microsoft Word 6.0 (or higher) word-processing documents with JD Edwards EnterpriseOne records to automatically print business documents. You can use MailMerge Workbench to print documents, such as form letters about verification of employment. A database connection where all database operations delay writing to the database until a call to commit is made.
logic server
MailMerge Workbench
Manual Commit transaction
master business function (MBF) An interactive master file that serves as a central location for adding, changing, and updating information in a database. Master business functions pass information between data entry forms and the appropriate tables. These master functions provide a common set of functions that contain all of the necessary default and editing rules for related programs. MBFs contain logic that ensures the integrity of adding, updating, and deleting information from databases. master table matching document See published table. A document associated with an original document to complete or change a transaction. For example, in JD Edwards EnterpriseOne Financial Management, a receipt is the matching document of an invoice, and a payment is the matching document of a voucher. Files that use one of the following naming conventions that are not organized into table format: Gxxx, xxxGT, or GTxxx. A central location for sending and receiving all JD Edwards EnterpriseOne messages (system and user generated), regardless of the originating application or user. An interoperability model that enables third-party systems to connect to JD Edwards EnterpriseOne to exchange information through the use of messaging queues. A server that handles messages that are sent for use by other programs using a messaging API. Messaging servers typically employ a middleware program to perform their functions. A BPEL/ESB server that is installed within an application server. An EnterpriseOne tool provided for an administrator to get statistical information for various EntepriseOne servers, reset statistics, and set notifications.
media storage object message center messaging adapter messaging server
Middle-Tier BPEL/ESB Server Monitoring Application
38
Glossary
named event rule (NER)
Encapsulated, reusable business logic created using event rules, rather that C programming. NERs are also called business function event rules. NERs can be reused in multiple places by multiple programs. This modularity lends itself to streamlining, reusability of code, and less work. In Brazil, a legal document that must accompany all commercial transactions for tax purposes and that must contain information required by tax regulations. In Brazil, a nota fiscal with invoice information. See also nota fiscal.
nota fiscal nota fiscal factura
Object Configuration Manager (OCM)
In JD Edwards EnterpriseOne, the object request broker and control center for the runtime environment. OCM keeps track of the runtime locations for business functions, data, and batch applications. When one of these objects is called, OCM directs access to it using defaults and overrides for a given environment and user. A repository of all versions, applications, and business functions reusable in building applications. Object Librarian provides check-out and check-in capabilities for developers, and it controls the creation, modification, and use of JD Edwards EnterpriseOne objects. Object Librarian supports multiple environments (such as production and development) and enables objects to be easily moved from one environment to another. A process that blends any modifications to the Object Librarian in a previous release into the Object Librarian in a new release. An interoperability model that enables you to use SQL statements to extract JD Edwards EnterpriseOne data for summarization and report generation. An interoperability model that enables you to set up an interface for JD Edwards EnterpriseOne to pass data to another software package, such as Microsoft Excel, for processing. JD Edwards EnterpriseOne objects are installed to workstations in packages from the deployment server. A package can be compared to a bill of material or kit that indicates the necessary objects for that workstation and where on the deployment server the installation program can find them. It is point-in-time snapshot of the central objects on the deployment server. A software application that facilitates the deployment of software changes and new applications to existing users. Additionally, in JD Edwards EnterpriseOne, a package build can be a compiled version of the software. When you upgrade your version of the ERP software, for example, you are said to take a package build. Consider the following context: Also, do not transfer business functions into the production path code until you are ready to deploy, because a global build of business functions done during a package build will automatically include the new functions. The process of creating a package build is often referred to, as it is in this example, simply as a package build.
Object Librarian
Object Librarian merge Open Data Access (ODA) Output Stream Access (OSA)
package
package build
package location
The directory structure location for the package and its set of replicated objects. This is usually \\deployment server\release\path_code\package\package name. The subdirectories under this path are where the replicated objects for the package are placed. This is also referred to as where the package is built or stored. An application that, during the Installation Workbench process, transfers the package information tables from the Planner data source to the system-release number data source. It also updates the Package Plan detail record to reflect completion. The specific portion of the file system on the EnterpriseOne development client where EnterpriseOne development artifacts are stored.
Package Workbench
Pathcode Directory
39
Glossary
patterns
General repeatable solutions to a commonly occurring problem in software design. For business service development, the focus is on the object relationships and interactions. For orchestrations, the focus is on the integration patterns (for example, synchronous and asynchronous request/response, publish, notify, and receive/reply). A means of grouping end items whose similarity of design and manufacture facilitates being planned in aggregate. The ability to define default values for specified fields for a user-defined hierarchy of items, item groups, customers, and customer groups. The interface between a printer and a network that enables network clients to connect to the printer and send their print jobs to it. A print server can be a computer, separate hardware device, or even hardware that resides inside of the printer itself. A JD Edwards EnterpriseOne environment used to test unaltered objects with JD Edwards EnterpriseOne demonstration data or for training classes. You must have this environment so that you can compare pristine objects that you modify. A data structure that enables users to supply parameters that regulate the running of a batch program or report. For example, you can use processing options to specify default values for certain fields, to determine how information appears or is printed, to specify date ranges, to supply runtime values that regulate program execution, and so on. A JD Edwards EnterpriseOne environment in which users operate EnterpriseOne software. A file server that has been quality assurance tested and commercialized and that is usually provided in conjunction with user support services. Published business services web service deployed to a production application server. A representation of changes to JD Edwards EnterpriseOne software that your organization receives on magnetic tapes or disks. In JD Edwards EnterpriseOne, a virtual container for objects being developed in Object Management Workbench. The designated path for advancing objects or projects in a workflow. The following is the normal promotion cycle (path): 11>21>26>28>38>01 In this path, 11 equals new project pending review, 21 equals programming, 26 equals QA test/review, 28 equals QA test/review complete, 38 equals in production, 01 equals complete. During the normal project promotion cycle, developers check objects out of and into the development path code and then promote them to the prototype path code. The objects are then moved to the productions path code before declaring them complete.
planning family preference profile print server
pristine environment
processing option
production environment production-grade file server Production Published Business Services Web Service program temporary fix (PTF) project promotion path
proxy server published business service
A server that acts as a barrier between a workstation and the internet so that the enterprise can ensure security, administrative control, and caching service. EnterpriseOne service level logic and interface. A classification of a published business service indicating the intention to be exposed to external (non-EnterpriseOne) systems. Information about a published business service used to determine relevant authorization records. Published business services + method name, published business services, or *ALL.
published business service identification information
40
Glossary
published business service web service published table
Published business services components packaged as J2EE Web Service (namely, a J2EE EAR file that contains business service classes, business service foundation, configuration files, and web service artifacts). Also called a master table, this is the central copy to be replicated to other machines. Residing on the publisher machine, the F98DRPUB table identifies all of the published tables and their associated publishers in the enterprise. The server that is responsible for the published table. The F98DRPUB table identifies all of the published tables and their associated publishers in the enterprise. One of the JD Edwards EnterpriseOne methods for replicating data to individual workstations. Such machines are set up as pull subscribers using JD Edwards EnterpriseOne data replication tools. The only time that pull subscribers are notified of changes, updates, and deletions is when they request such information. The request is in the form of a message that is sent, usually at startup, from the pull subscriber to the server machine that stores the F98DRPCN table. An abbreviation for query by example. In JD Edwards EnterpriseOne, the QBE line is the top line on a detail area that is used for filtering data. A message triggered from EnterpriseOne application logic that is intended for external systems to consume. A function used to modify JD Edwards EnterpriseOne software, or subset of it, such as a table or business data, so that it functions at a new release or cumulative update level, such as B73.2 or B73.2.1. A server that is responsible for replicating central objects to client machines. Unique data identifying a browser session that initiates the business services call request host/port user session. Mandatory guidelines that are not enforced by tooling, but must be followed in order to accomplish the desired results and to meet specified standards. In JD Edwards Procurement and Subcontract Management, a request from a supplier for item and price information from which you can create a purchase order. In JD Edwards Sales Order Management, item and price information for a customer who has not yet committed to a sales order.
publisher pull replication
QBE real-time event refresh
replication server Rt-Addressing rules quote order
secure by default Secure Socket Layer (SSL)
A security model that assumes that a user does not have permission to execute an object unless there is a specific record indicating such permissions. A security protocol that provides communication privacy. SSL enables client and server applications to communicate in a way that is designed to prevent eavesdropping, tampering, and message forgery. A Java class that implements the methods that declare in a Service Endpoint Interface (SEI). Found on JD Edwards EnterpriseOne menus, a selection represents functions that you can access from a menu. To make a selection, type the associated number in the Selection field and press Enter. The process of converting an object or data into a format for storage or transmission across a network connection link with the ability to reconstruct the original data or objects when needed. An application that, during the Installation Workbench process, copies the server configuration files from the Planner data source to the system-release number
SEI implementation selection
serialize
Server Workbench
41
Glossary
data source. The application also updates the Server Plan detail record to reflect completion. Service Endpoint Interface (SEI) SOA softcoding source repository spot rate Specification merge A Java interface that declares the methods that a client can invoke on the service. Abbreviation for Service Oriented Architecture. A coding technique that enables an administrator to manipulate site-specific variables that affect the execution of a given process. A repository for HTTP adapter and listener service development environment artifacts. An exchange rate entered at the transaction level. This rate overrides the exchange rate that is set up between two currencies. A merge that comprises three merges: Object Librarian merge, Versions List merge, and Central Objects merge. The merges blend customer modifications with data that accompanies a new release. A complete description of a JD Edwards EnterpriseOne object. Each object has its own specification, or name, which is used to build applications. An application that, during the Installation Workbench process, runs the batch applications that update the specification tables. A special message signed by a certificate authority that contains the name of a user and that users public key in such a way that anyone can "verify" that the message was signed by no one other than the certification authority and thereby develop trust in the users public key. The mode of processing that enables users who are disconnected from a server to enter transactions and then later connect to the server to upload those transactions. Table F98DRSUB, which is stored on the publisher server with the F98DRPUB table and identifies all of the subscriber machines for each published table. An inheritance concept of the Java language where a class is an instance of something, but is also more specific. Tree might be the superclass of Oak and Elm, for example. Any type of information that is not maintained in a master file. Supplemental data is usually additional information about employees, applicants, requisitions, and jobs (such as an employees job skills, degrees, or foreign languages spoken). You can track virtually any type of information that your organization needs. For example, in addition to the data in the standard master tables (the Address Book Master, Customer Master, and Supplier Master tables), you can maintain other kinds of data in separate, generic databases. These generic databases enable a standard approach to entering and maintaining supplemental data across JD Edwards EnterpriseOne systems. table access management (TAM) The JD Edwards EnterpriseOne component that handles the storage and retrieval of use-defined data. TAM stores information, such as data dictionary definitions; application and report specifications; event rules; table definitions; business function input parameters and library information; and data structure definitions for running applications, reports, and business functions. An interoperability model that enables the exchange of information between JD Edwards EnterpriseOne and third-party systems using non-JD Edwards EnterpriseOne tables.
specification Specification Table Merge Workbench SSL Certificate
store-and-forward subscriber table superclass
supplemental data
Table Conversion Workbench
42
Glossary
table conversion
An interoperability model that enables the exchange of information between JD Edwards EnterpriseOne and third-party systems using non-JD Edwards EnterpriseOne tables. Logic that is attached to database triggers that runs whenever the action specified by the trigger occurs against the table. Although JD Edwards EnterpriseOne enables event rules to be attached to application events, this functionality is application specific. Table event rules provide embedded logic at the table level. A server that enables terminals, microcomputers, and other devices to connect to a network or host computer or to devices attached to that particular computer. The task of entering, reviewing and approving, and posting batches of transactions in JD Edwards EnterpriseOne. In JD Edwards Procurement and Subcontract Management, the process of comparing receipt information to suppliers invoices to create vouchers. In a three-way match, you use the receipt records to create vouchers. A monitor that controls data transfer between local and remote terminals and the applications that originated them. TP monitors also protect data integrity in the distributed environment and may include programs that validate data and format terminal screens. A method related to the management of a manual commit transaction boundary (for example, start, commit, rollback, and cancel). An electronic business transaction (electronic data interchange standard document) made up of segments. One of several events specific to data dictionary items. You can attach logic to a data dictionary item that the system processes automatically when the event occurs. A specific workflow event that requires special action or has defined consequences or resulting actions. An authentication mechanism in which both client and server authenticate themselves by providing the SSL certificates to each other. In JD Edwards Procurement and Subcontract Management, the process of comparing purchase order detail lines to the suppliers invoices to create vouchers. You do not record receipt information. User ID, role, or *public. Adds new user override records into a customers user override table. A specific type of source file that holds input or output data, much like a data structure passes data. Value objects can be exposed (used in a published business service) or internal, and input or output. They are comprised of simple and complex elements and accessories to those elements. In JD Edwards Capital Asset Management, the difference between revenue generated by a piece of equipment and costs incurred by the equipment. In JD Edwards EnterpriseOne Project Costing and JD Edwards EnterpriseOne Manufacturing, the difference between two methods of costing the same item (for example, the difference between the frozen standard cost and the current cost is an engineering variance). Frozen standard costs come from the Cost Components table, and the current costs are calculated using the current bill of material, routing, and overhead rates.
table event rules
terminal server three-tier processing three-way voucher match
transaction processing (TP) monitor
transaction processing method transaction set trigger triggering event two-way authentication two-way voucher match
user identification information User Overrides merge value object
variance
43
Glossary
versioning a published business service Version List merge
Adding additional functionality/interfaces to the published business services without modifying the existing functionality/interfaces. The Versions List merge preserves any non-XJDE and non-ZJDE version specifications for objects that are valid in the new release, as well as their processing options data. Forms that can be invoked from a control via a trigger to assist the user in determining what data belongs in the control. An alternate description for a data dictionary item that appears on a specific JD Edwards EnterpriseOne form or report. An internal type of a wide character. It is used for writing portable programs for international markets. A web server that enables web applications to exchange data with the back-end systems and databases used in eBusiness transactions. A server that sends information as requested by a browser, using the TCP/IP set of protocols. A web server can do more than just coordination of requests from browsers; it can do anything a normal server can do, such as house applications or data. Any computer can be turned into a web server by installing server software and connecting the machine to the internet. An XML format for describing network services. An XML format for assisting in the inspection of a site for available services and a set of rules for how inspection-related information should be made. Foundation classes for web service proxy that must be included in a business service server artifact for web service consumption on WAS. An XML document that contains values that are used to configure a web service proxy. This document identifies the endpoint and conditionally includes security information. An XML document that provides the structure for a soft coded record. The portion of a database operation that specifies which records the database operation will affect. A multiuser server that enables terminals and minimally configured computers to display Windows applications even if they are not capable of running Windows software themselves. All client processing is performed centrally at the Windows terminal server and only display, keystroke, and mouse commands are transmitted over the network to the client terminal device. A type of JDeveloper extension used to walk the user through a series of steps. A program that enables users to access a group of related programs from a single entry point. Typically, the programs that you access from a workbench are used to complete a large business process. For example, you use the JD Edwards EnterpriseOne Payroll Cycle Workbench (P07210) to access all of the programs that the system uses to process payroll, print payments, create payroll reports, create journal entries, and update payroll history. Examples of JD Edwards EnterpriseOne workbenches include Service Management Workbench (P90CD020), Line Scheduling Workbench (P3153), Planning Workbench (P13700), Auditors Workbench (P09E115), and Payroll Cycle Workbench. In JD Edwards EnterpriseOne Manufacturing, a calendar that is used in planning functions that consecutively lists only working days so that component and work order scheduling can be done based on the actual number of work days available. A work
visual assist vocabulary override wchar_t web application server web server
Web Service Description Language (WSDL) Web Service Inspection Language (WSIL) web service proxy foundation web service softcoding record web service softcoding template Where clause Windows terminal server
wizard workbench
work day calendar
44
Glossary
day calendar is sometimes referred to as planning calendar, manufacturing calendar, or shop floor calendar. workflow The automation of a business process, in whole or in part, during which documents, information, or tasks are passed from one participant to another for action, according to a set of procedural rules. A server that usually contains subsets of data replicated from a master network server. A workgroup server does not perform application or batch processing. A service that uses system calls to capture JD Edwards EnterpriseOne transactions as they occur and then calls third-party software, end users, and other JD Edwards EnterpriseOne systems that have requested notification when the specified transactions occur to return a response. An interoperability capability that enables you to call business functions. An interoperability capability that provides a single point of entry for all XML documents coming into JD Edwards EnterpriseOne for responses. An interoperability capability that enables you to request and receive JD Edwards EnterpriseOne database information in chunks. An interoperability capability that enables you to request events from one JD Edwards EnterpriseOne system and receive a response from another JD Edwards EnterpriseOne system. An interoperability capability that enables you to use a predefined transaction type to send information to or request information from JD Edwards EnterpriseOne. XML transaction uses interface table functionality. Transforms an XML document that is not in the JD Edwards EnterpriseOne format into an XML document that can be processed by JD Edwards EnterpriseOne. XTS then transforms the response back to the request originator XML format. A service that uses interface table functionality to capture JD Edwards EnterpriseOne transactions and provide notification to third-party software, end users, and other JD Edwards EnterpriseOne systems that have requested to be notified when certain transactions occur. A working table where non-JD Edwards EnterpriseOne information can be stored and then processed into JD Edwards EnterpriseOne. Z tables also can be used to retrieve JD Edwards EnterpriseOne data. Z tables are also known as interface tables. Third-party data that is properly formatted in interface tables for updating to the JD Edwards EnterpriseOne database.
workgroup server XAPI events
XML CallObject XML Dispatch XML List XML Service
XML Transaction
XML Transaction Service (XTS) Z event
Z table
Z transaction
45
Glossary
46
Index
Numerics/Symbols
76B/GE (Government Entities) 7 76B/TT (Transaction Nature Items) 7 Service Nota Fiscal Withholding Amount by Service (F76B428) 20 Service Nota Fiscal Withholding Amounts by Formula (F76B427) 20 setting up minimum amounts for sales withholding 11 SO Accumulated withholdings by CO and AN8 (F76B424) 21 SO Brazil Withholding Additional Info (P76B4210) 13 SO Brazil Withholding Additional Information form 16 stand-alone notas fiscais withholding for the sale of services 25 Withholding Concepts Setup form 9 withholding on sale of services, See withholding on sale of services Work with ISS Exempt Percentages form 10
A
additional documentation x application fundamentals ix
B
Brazil 76B/GE (Government Entities) 7 76B/TT (Transaction Nature Items) 7 F76B422 (Minimum Amount to Withhold) 21 F76B424 (SO Accumulated withholdings by CO and AN8) 21 F76B427 (Service Nota Fiscal Withholding Amounts by Formula) 20 F76B428 (Service Nota Fiscal Withholding Amount by Service) 20 Minimum Amount to Withhold (F76B422) 21 Minimum Amount to Withhold (P76B422) 11 Minimum Amount to Withhold form 11 Nota Fiscal Withholdings (P76B4220) 25 P76B106 (Services ISS Exempt) 8 P76B421 (Withholding Concepts Setup BR) 8 P76B4210 (SO Brazil Withholding Additional Info) 13 P76B422 (Minimum Amount to Withhold) 11 P76B4220 (Nota Fiscal Withholdings) 25 R76559B (Reverse/Void Nota Fiscal) service notas fiscais 24 R76588B (Generate Nota Fiscal) calculations for withholding on sales 19 Reverse/Void Nota Fiscal (R76559B) service notas fiscais 24 sales order processing withholding on sale of services 13
C
comments, submitting xiii common fields xiii contact information xiii cross-references xii
D
documentation downloading x related x updates x downloading documentation
F
F76B422 (Minimum Amount to Withhold) 21 F76B424 (SO Accumulated withholdings by CO and AN8) 21 F76B427 (Service Nota Fiscal Withholding Amounts by Formula) 20 F76B428 (Service Nota Fiscal Withholding Amount by Service) 20
47
Index
I
implementation guides ordering x
T
typographical conventions xi
M
Minimum Amount to Withhold (P76B422) 11 Minimum Amount to Withhold form (BRA) 11
V
visual cues xii
W
warnings xii Withholding Concepts Setup BR (P76B421) 8 Withholding Concepts Setup form (BRA) 9 withholding for the sale of services Minimum Amount to Withhold form 11 P76B4210 (SO Brazil Withholding Additional Info) 13 P76B4220 (Nota Fiscal Withholdings) 25 Reverse/Void Nota Fiscal (R76559B) 24 sales order processing default values 14 overview 13 validations 15 SO Brazil Withholding Additional Information form 16 Withholding Concepts Setup form 9 Work with ISS Exempt Percentages form 10 XML fields 29 withholding on sale of services 76B/GE (Government Entities) 7 76B/TT (Transaction Nature Items) 7 changes to applications 6 overview 3 withholding on sales of services process flow 4 withholding on the sale of services calculations overview 20 Minimum Amount to Withhold (F76B422) 21 minimum monthly basis amounts example 22 minimum monthly basis amounts overview 21 nota fiscal validations 19 printing notas fiscais 27 process flow for withholding calculations 20
N
notes xii
O
Oracle MetaLink 3 x
P
P76B106 (Services ISS Exempt) 8 P76B421 (Withholding Concepts Setup BR) 8 P76B4210 (SO Brazil Withholding Additional Info) 13 P76B422 (Minimum Amount to Withhold) 11 P76B4220 (Nota Fiscal Withholdings) 25 PeopleCode, typographical conventions xi prerequisites ix
R
R76559B (Reverse/Void Nota Fiscal) service notas fiscais 24 R76560B (Print Nota Fiscal) withholding for the sale of services 27 withholding processing option 27 related documentation x
S
S.O. Brazilian Information Detail form 16 S.O. Brazilian Information Header form 16 Services ISS Exempt (P76B106) 8 SO Brazil Withholding Additional Info (P76B4210) 13 SO Brazil Withholding Additional Information form (BRA) 16 suggestions, submitting xiii
48
Index
R76588B (Generate Nota Fiscal) withholding calculations 19 Service Nota Fiscal Withholding Amount by Service (F76B428) 20 Service Nota Fiscal Withholding Amounts by Formula (F76B427) 20 setting up ISS exemptions 8 minimum amounts for sales withholding 11 tax type codes 8 withholding concepts 8 SO Accumulated withholdings by CO and AN8 (F76B424) 21 stand-alone notas fiscais 25 Withholding Concepts Setup BR (P76B421) 8 Work with ISS Exempt Percentages form (BRA) 10
49
Index
50

Localização Brasil - Serviços

Загружено:

Сведения о документе

Исходное описание:

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Localização Brasil - Serviços

Загружено:

Авторское право:

Доступные форматы

Working with Withholding for the Sale of Services in Brazil

Copyright 2009, Oracle and/or its affiliates. All rights reserved.

Copyright 2009, Oracle and/or its affiliates. All rights reserved.

Glossary of JD Edwards EnterpriseOne Terms.........................................................31

Copyright 2009, Oracle and/or its affiliates. All rights reserved.

Copyright 2009, Oracle and/or its affiliates. All rights reserved.

About This Documentation Preface

JD Edwards EnterpriseOne Application Prerequisites

Copyright 2009, Oracle and/or its affiliates. All rights reserved.

Documentation Updates and Downloading Documentation

Obtaining Documentation Updates

Copyright 2009, Oracle and/or its affiliates. All rights reserved.

Typographical Conventions and Visual Cues

Monospace font (quotation marks)

Copyright 2009, Oracle and/or its affiliates. All rights reserved.

Typographical Convention or Visual Cue [ ] (square brackets) & (ampersand)

Country, Region, and Industry Identifiers

Copyright 2009, Oracle and/or its affiliates. All rights reserved.

Comments and Suggestions

Common Fields Used in Implementation Guides

Copyright 2009, Oracle and/or its affiliates. All rights reserved.

Batch Date Batch Status

Copyright 2009, Oracle and/or its affiliates. All rights reserved.

Copyright 2009, Oracle and/or its affiliates. All rights reserved.

Copyright 2009, Oracle and/or its affiliates. All rights reserved.

Preface to Working with Withholding for the Sale of Services in Brazil

JD Edwards EnterpriseOne Products

JD Edwards EnterpriseOne Application Fundamentals

Copyright 2009, Oracle and/or its affiliates. All rights reserved.

Copyright 2009, Oracle and/or its affiliates. All rights reserved.

Getting Started With Withholding for the Sale of Services in Brazil

Integrations for Withholding for the Sale of Services in Brazil

Withholding for the Sale of Services in Brazil Implementation Overview

JD Edwards EnterpriseOne Brazil Localization Implementation Steps

Copyright 2009, Oracle and/or its affiliates. All rights reserved.

Getting Started With Withholding for the Sale of Services in Brazil

Step 3. Enter Brazil-specific information for address book records.

Reference The implementation guide for your release of Brazil localizations.

Copyright 2009, Oracle and/or its affiliates. All rights reserved.

Understanding Withholding for the Sale of Services in Brazil

Withholding for the Sale of Services in Brazil

Copyright 2009, Oracle and/or its affiliates. All rights reserved.

Understanding Withholding for the Sale of Services in Brazil

Copyright 2009, Oracle and/or its affiliates. All rights reserved.

Understanding Withholding for the Sale of Services in Brazil

Process flow for Withholding on the Sale of Services

Copyright 2009, Oracle and/or its affiliates. All rights reserved.

Understanding Withholding for the Sale of Services in Brazil

Copyright 2009, Oracle and/or its affiliates. All rights reserved.

Setting Up UDCs for Withholding for the Sale of Services

Government Entities (76B/GE)

Transaction Nature Items (76B/TT)

Copyright 2009, Oracle and/or its affiliates. All rights reserved.

Set up withholding concepts Specify exemptions to ISS withholding.

Copyright 2009, Oracle and/or its affiliates. All rights reserved.

Withholding Concepts Setup W76B421B

Work with ISS Exempt Percentages

ISS Withholding Setup (G76B41A), Service ISS Exempt

Setting Up Withholding Concepts

INSS Subject to Withh. (INSS subject to withholding)

Copyright 2009, Oracle and/or its affiliates. All rights reserved.

CSLL Subject to Withh. (CSLL subject to withholding) IRPJ Concept

IRPJ Subject to Withh. (IRPJ subject to withholding) PIS Concept