PNP validation

Hi experts,
i am preparing a payroll report using LOGICAL DATA BASE PNP screen and HR report category _X20001.
my requirment is to validate the value entered in the fields availble in the standard PNP screen in my code how can i do this.
Thanks and regards.
M.Phanindra

Hi,
Once selection screen is triggered put the cursor and press f1 in validation required field then one pop-up window comes with the details. Click on technical attributes button then u can see screenfield of that perticular field.
When u enter any value in that field, value can be captured at screenfield. With that screen field u can check what is entered. with that u can validate.
Regards,
Narendra Katuri.

Similar Messages

  • Selection screen validation when using PNP LDB

    Hi guys,
    I want to validate my selection screen parameters.Thats is if somebody wants to run the program without giving any input parameters to the selection screen(trying to run the report with a blank screen) I want to pop up an error/information message so that it will return the selection screen.I am using PNP Logical database for my selection screen.Please help.Thanks in advance.
    Thanks,
    Karthik.

    Welcome to SDN.
    If you are using PNP logical data base then validating the fields will be little tricky...
    You canc check all the other fields in START-OF-SELECTION and if they are empty return eroor. Remember all the field s on the scree... so I will suggest you to choose HR report Category accordingly.
    Also,when it comes to date field then you need to check for the start and end dates rather than blank fields as SAP defaulted them to system start and end date.
    Still, I will prefer to create a HE Report Category for the PNP database and use the screen while validating....that will be easy...

  • HR ABAP - PNP selection screen

    Hi Friends,
    I am executing the standard report with PNP logical database .
    But in the selection screen when I click on further selection and select the parameter company code.
    Now I entered the company code "0060", but I am getting the out put for both company code 0060 and 0020,
    here I need the out put only for the person which are belongs to company code 0060, but I think the selection screen company code was not controlling the out put.
    Also I checked the Infotype internal table p0001, here I am able to see both the company codes, and for that person the process is continuing and I am getting the out put for the company code 0020, bcz the current/valid record for this person is 0020.
    Request to let me know any issue there?
    Magesh.S

    Hi,
    You need to set "person selection period" dates, in order to list values with selected parameters.
    Daniel

  • PC Suite install freezes with "PnP Manager busy" l...

    Hi,
    I am trying to install Nokia PC Suite 6.86.9.0, but the installer freezes consistently at 54% progress.
    It is possible to click the red "abort" button but it wont stop the installer, instead it must be killed from task manager. The process called DPINST.EXE seems to be the culprit. It leaves the following message in the C:\WINDOWS\DPINST.LOG file:
    INFO: ****************************************
    INFO: 04/22/2008 16:38:23
    INFO: Product Version 2.1.0.0.
    INFO: Version: 5.1.2600 Service Pack 2
    INFO: Platform ID: 2 (NT)
    INFO: Service Pack: 2.0
    INFO: Suite: 0x0100, Product Type: 1
    INFO: Architecture: X86.
    INFO: Interactive Windows Station
    INFO: Command Line: '"C:\Program Files\PC Connectivity Solution\dpinst.exe" /LM /SA /SW'
    INFO: DPInst is a multi-lingual binary.
    INFO: ****************************************
    INFO: Current working directory: 'C:\Program Files\PC Connectivity Solution'
    INFO: Running on path 'C:\Program Files\PC Connectivity Solution'
    INFO: No valid 'dpinst.xml' file provided.
    INFO: Install option set: Suppressing Wizard but no OS popups.
    INFO: Install option set: legacy mode on.
    INFO: Install option set: Suppress Add or Remove Programs entries.
    INFO: Found driver package: 'C:\Program Files\PC Connectivity Solution\PCCSMCFD.inf'.
    INFO: Found driver package: 'C:\Program Files\PC Connectivity Solution\PCCSWpdDriver.inf'.
    INFO: Found driver package: 'C:\Program Files\PC Connectivity Solution\PCCS_Bluetooth.inf'.
    INFO: PnP Manager busy, waiting until it processed the pending install events.
    INFO: ****************************************
    My system information (OS, service pack, etc. can also be seen in the log message).
    Googling "PnP Manager busy" does not yield any useful information.
    I have also tried cleaning my system with Nokia PC Suite Cleaner 3.6 before reinstalling but to no avail.
    Any ideas how to fix this?
    Best regards,
    Jake
    Attachments:
    DPINST1.LOG ‏2 KB

    Finally found the solution:
    The registry keyFactoryPreInstallInProgressin HKEY_LOCAL_MACHINE\System\Setup was defined.
    After deleting this key, the install went smoothly.
    See this post for further info:
    http://forums.windrivers.com/showthread.php?t=65537
    /jake

  • PNP - Selection scr een

    Hi Friends,
    I have one doubt on selection screen of logical database PNP.
    I enter the date in selection screen as 01.06.2006 to 31.12.2006 for both data selection and person selection.
    In the database table date(begda) is 01.01.2000.
    When i use provide * from p0001 between pn-begda and pn-endda..endprovide,
    it automatically changes the date in table to selection screen date, ie from 01.01.2000 to 01.01.2006. So brings all the data even though date in table exists only up to 01.01.2000. How can i solve this?
    Thanks in advance.

    No, i want all the records for a person during a particular period. All actions from pa0000. Now i validated the data selection between loop-endloop. But it does not validate the person selection. Any idea Please.
    Thanks

  • GPIB/TNT PnP DOS Installation Issue

    I have a AT-GPIB/TNT PnP board that I am trying to install on a DOS computer.  I am using the latest NI488.2 software for DOS.
    On bootup, the GPIB software drivers install properly, but the interface cannot be found.  When I run ibdiag it detects the correct board but then I get errors saying :
    1. Make sure the GPIB cables are disconnected.
    2. The base address does not match the address in the ni-pnp.ini file. 
    3. Another board or device is using the same address space. Try using a different I/O address and run the hardware diagnostic program.
    I don't have any cables connected ot the card.  The base address (as set using ibconf.exe) does match the address settings in the ni-pnp.ini file.  I have tried every possible base address with the IRQ and DMA turned off just to make sure that these were not in conflict.  I have tried other ISA slots in the computer.  I have disabled other on-board devices in the BIOS to prevent potential conflicts.  I have a PCI IO board also in the system.  But I have tried changing the addresses with and without this board installed.
    Based on the errors, it feels like the address settings may not be making it to the card properly, so that there is an address mismatch between what the computer/driver thinks is installed and what the card thinks it's address actually is.
    Any ideas?

    Jesse,
    Thanks for the reply.  
    I followed one of the links and read the following (I highlighted the critical portions in bold/underline):
    If ibdiag completes with no errors, your hardware is functioning properly. If ibdiag returns an error message, go back to the previous step and reconfigure the board to not use a DMA channel or an IRQ. Then shut down the computer, remove the IRQ, DACK, and DRQ jumpers, and boot up again. Rerun the hardware diagnostic test. At this point only the board's base I/O address is being tested. If the diagnostic continues to fail, then there are only three possible reasons:
    The Base I/O Address selected has a conflict with another hardware component in your computer. You should try other addresses, being certain to modify the DIP switches and ibconf settings each time.
    The Base I/O Address selected in ibconf is not a legal address. If using a Non-Plug and Play board, the Base I/O Address selected in ibconf does not match the DIP switch settings on the board. Sometimes users accidentally set the switches exactly opposite of what they should be. Be certain that you are following the switch diagram given in ibconf correctly.
    Note: The AT-GPIB/TNT (PnP) and AT-GPIB/TNT+ have valid address ranges of 0x0100 to 0x03E0 in increments of 0x20 bytes.
    The board has been damaged and needs repair. Call National Instruments if you feel this is the case.
    I worked the drill as described and I believe that the hardware is not working properly.  I will call NI.
    Thanks again.

  • Difference between PNP and PCH logical database

    WHats the difference between PNP nd PCH? When to use which??
    Tx

    Hi,
    The Difference is only with in an SAP R/3 system in which Concurrent Employment is active, reports are executed by the PNPCE logical database. The general logic of the PNPCE logical database corresponds to the PNP logical database. The PNPCE logical database can also process the concept of Concurrent Employment.
    HR Logical Databases
    In Human Resources (HR), the following logical databases can be used as a data source for HR InfoSets:
    PNP (PNPCE)
    PAP
    PCH
    By selecting a logical database, you determine the HR data that can be reported on using an InfoSet.
    Logical Database PCH
    This logical database generally enables you to report on all HR infotypes. However, you are advised not to use this logical database unless you want to report on Personnel Planning data.
    Logical Database PNP (or PNPCE)
    Use logical database PNP to report on HR master data. It is possible to use logical database PCH to access this data, but PNP meets such reporting requirements more quickly because it is best suited to the task of selecting persons.
    Logical database PNP enables you to access HR master data and infotypes from Personnel Planning. For example, you have the following options:
    Reporting on the costs, number of attendees booked, and instructor for a business event on which an employee is booked
    Reporting on working time and planned compensation for a position that an employee occupies
    Reporting on the validity and proficiency of a qualification that an employee fulfils
    From a technical perspective, this means you can use PNP to report on all of the infotypes that exist for objects (infotype 1000) that have a direct relationship (infotype 1001) with the Person object.
    The ability to access infotypes from Personnel Planning using logical database PNP is a special feature that you can only use in the context of SAP Query and Ad Hoc Query. You cannot use this functionality for ABAP reports you programmed yourself.
    You can also use logical database PNP to report on data from Personnel Time Management (infotypes 2000 to 2999) and Payroll (special payroll infotypes for the USA and customer infotypes; for more information, access Customizing for the Human Resources Information System and see Payroll Results).
    Logical Database PAP
    Logical database PAP enables you to access data from Recruitment.
    Check this link for more details
    http://help.sap.com/saphelp_erp2004/helpdata/en/e1/e1f83f6e5a11d687620000e82158f1/frameset.htm
    <b>Reward points</b>
    Regards

  • PNP standard screen Reporting period

    Hi All,
    The PNP standard screen has a parameter Reporting period.
    Could anyone please explain that if I select a Key date then what will this date be matched against in the database? Will it be the begda of an infotype?
    Also, same with selecting "other period" what would this range be checked against?
    I would appreciate your help.
    Regards,
    ~Mark

    Hi,
    When you select Key Date, all the employee records fetched which valid as on the Key date (i.e. All the records with BEGDA < KEYDATE < ENDDATE).
    Similarly for other field, employee records are fetched as on valid on the range given in the 'other period'.
    Hope this helps,
    Shrinivas

  • PCL PNP HR Change data retrieval

    Dear Friends,
    I need to develop a report which retrieves all changed data for the specific period specified by the user.
    1) I am not very sure if I need to use PCL4 or any other clustertable, or I can still go with PNP and do query RP_PROVIDE <OLD DATE> <OLDDATE1>!!!
    2) If I need to use cluster table could any of you please provide me sample code snippet thus I can go a head?
    Thanks and Regards,
    Joy
    Below are the entries and different infotypes for which the changed data list needs to be displayed.
    PA0002     Forename     VORNA
    PA0002     Name at birth     NAME2
    PA0002     Last Name     NACHN
    PA0002     Middle Name     MIDNM
    PA0002     Known As     RUFNM
    PA0001     Company Code     BUKRS
    PA0002     Birth Date     GBDAT
    PA0077     Ethnic Origin     RACKY
    PA0002     Gender     GESCH
    PA0002     Marital Status     FAMST
    PA0002     Name Suffix     TITL2
    PA0105     Email Address     USRID_LONG
    PA0002     Title     TITEL
    PA0006     Fax     NUMXX
    PA0006     Mobile     NUMXX
    PA0002     Nationality     NATIO
    PA0006     Domicile     LAND1
    PA0002     Religion     KONFE
    PA0702     Passport     TBD
    PA0702     Place of issue     TBD
    PA0702     Issue date     TBD
    PA0702     Valid till     TBD
    PA0041     Date of Hire     DATXX
    PA0000     Action Reason     MASSG
    PA0001
    HRP1001
    PA0002     Reporting to     ORGEH
    OBJID/SOBID
    CNAME
    PA0041     Date of exit interview     DATXX
    PA0041     Leave Date     DATXX
    PA0000     Leaving Reason     MASSG
    PA0006     Street     STRAS
    PA0006     Address Line2     LOCAT
    PA0006     City     ORT01
    PA0006     District     ORT02
    PA0006     Region     STATE
    PA0006     Country     LAND1
    PA0006     Postal Code     PSTLZ
    PA0006     Communication Number     NUMXX
    PA0002     Personal ID     PERID
    PA0041     Date Of Last Hire
         DATXX
    PA0001     Location     BTRTL
    PA0007     Part time flag
         TEILK
    PA0001     Job
         STELL
    PA0001     Payroll area
         ABKRS
    HRP1000     OrgLvl1     OBJID
    PA0001     OrgLvl2     
    HRP1000     OrgLvl3     OBJID
    HRP1000     OrgLvl4     OBJID
    PA0000     Personnel Number     PERNR
    PA0041     Date of seniority     DATXX
         EEBankName     
    PA0009     Bank account no     BANKN
    PA0009     Bank account type     BNKSA
    PA0002     PERID

    Hi,
    Go through this link.
    change document for HR data
    Regards
    Sudheer

  • Change of LDB from PNP to PNPCE

    HI All,
       I have a HR program where LDB PNP is used. Now I need to change the LDB from PNP to PNPCE. Can any one please tell me what are the mandatory change I need to do in the program after changing the LDB.
    Thanks & Regards,
    Arnab

    Hi,
    Purpose
    The PNPCE logical database supports the evaluation of HR master data. It includes the functions of the PNP logical database and offers additional evaluation options. Therefore, you should use the PNPCE logical database instead of the PNP logical database for all new developments.
    The enhanced functionality of PNPCE in comparison to PNP essentially concerns the evaluation of Concurrent Employment, that is the possibility to group evaluate several assignments/personnel numbers of a person. The new events 'GET PERSON' and 'GET GROUP' as well as an enhanced syntax for the INFOTYPES statement (addition AS PERSON TABLE) for the procurement of infotype data enable you to use the new functionality. The use of these new functions is optional. You can run a PNPCE report that does not use the new events and the addition for the INFOTYPES statement in a PNP-compatible session. Since the PNPCE also has an improved selection screen, each report benefits from this even if the report does not use the functions for evaluating Concurrent Employment.
    Prerequisites
    A report that wants to use the PNPCE must enter this in its report attributes under Logical database.
    In addition, the PERNR structure must be declared in the report using the 'TABLES PERNR' statement. You can only use the PERNR structure again in certain circumstances. The use of the 'GET PERNR' event is therefore forbidden. Instead, use the 'GET PERAS' event. Except for the PERNR-PERNR component, all other components of the PERNR structure are no longer filled and have initial values. This kind of programming (with the exception of PERNR-PERNR) therefore not permitted.
    In addition to the 'GET PERAS' event, you can also use the GET PERSON' and 'GET GROUP' events. To be able to use these events, you must declare them using the NODES statement (NODES PERSON', 'NODES GROUP', or. NODES PERAS').
    Explanation of Terms
    If the 'GET PERSON' and 'GET GROUP events and the 'AS PERSON TABLE' addition for the INFOTYPES statement are not used, the report indicates that it does not require the functionality for evaluating Concurrent Employment. In this case, the report runs in a PNP-compatible session. This is referred to as PNP mode in the following documentation. On the other hand, if the report uses the functionality for evaluating Concurrent Employment we refer to CE mode.
    Features
    Process of an Evaluation
    The PNPCE selection screen offers you as standard a range of functions that you can use to restrict the personnel number and person selection. These are discussed in more detail in the following sections. The process is initially as follows regardless of whether the report runs in CE or PNP mode. All available functions and selection conditions leads to the selection of personnel numbers. If you use the sorting function, this set of personnel numbers is then sorted according to the sort criteria you selected. In PNP mode, the GET PERAS event is triggered as a result for each personnel number.
    In CE mode, the persons belonging to the personnel numbers are determined first for all personnel numbers selected. The GET PERSON event is then triggered for each person. The person ID is specified in the OBJID component of the PERSON structure. PERNR_NUM contains the total number of personnel assignments (= personnel numbers) that this person has and the ALL_PERNRS table, which contains a list of these personnel numbers regardless of whether they were actually selected or not. The SELECTED flag is set to X for the personnel numbers selected. The flag is initial for all personnel numbers that are not selected. The PROCESS flag specifies whether the personnel number should be processed in the rest of the process. This flag is set to X by default for the personnel numbers selected. However, the report can set or delete this flag at the GET PERSON event for all personnel numbers. In this way, report and logical database communicate with each other which enables the report to control the rest of the process.
    In the next step, the logical database groups all personnel numbers of a person that are to be processed (that is, all personnel numbers that have the PROCESS flag set). The report can control the type of grouping using the PNPCE_GROUPING_FROM_PAYROLL flag (normal or payroll grouping) and using the PNPGPRSN (grouping reason) and PNPGPVAL (grouping value) parameters of the selection screen. The GET GROUP event is triggered for each group of personnel numbers determined. The GROUPING_REASON and GROUPING_VALUE components contain the grouping reason and grouping value of this group. The number of personnel numbers that belong to this group and that are processed subsequently is in PERNR_NUM. The included ALL_PERNR table contains a list of these personnel numbers with additional information. The SELECTED flag specifies whether the current personnel number was originally selected (flag is set) or was marked by the report as to be processed. GROUPING_BEGDA and GROUPING_ENDDA contain the validity period that the personnel number has for this grouping. The NO_AUTHORITY flag is set if there is insufficient authorization for a personnel number. This personnel number is not processed further. The SORT component defines a standard sort order for the personnel numbers of a group. The report can change this by overwriting the values. In this way, report and logical database communicate with each other, which controls the further processing sequence of the personnel numbers.
    The GET PERAS event is then triggered for all personnel numbers of the group (with the exception of the personnel numbers for which no authorization exists) in the sequence defined by the SORT component (see above). The SELECTED, GROUPING_BEGDA, and GROUPING_ENDDA components have the same meaning here as with the GET GROUP event. The PROCESSED_BEFORE flag specifies whether the personnel number has already been processed once before (it is possible that the personnel number belongs to several groupings and has been therefore been processed several times).
    Thanks and Regards
    Ravi

  • Tuning LDB PNP

    Hi all,
    Can any one tell me how to optimize data retrival in PNP LDB.

    Hi,
    Use the following statement to restrict selection by dates.
    infotypes : 0008 VALID FROM date1 TO date2.
    I don't think you have the GET dbatb FIELDS option with the PNP Logical database. You just have to use loop at p0008 where ansal =...
    Regards,
    Suresh Datti

  • Microsoft.BDD.PnPEnum.exe is not a valid win32 application

    Hi all, Im running into an unusual bug during my media based Win 7 32 bit light touch deployment. After the wizrad completes and it formats the drives right about the time its ready to inject the drivers i get an error
    E:\Deploy\Tools\X86\Microsoft.DBB.PnPEnum.exe is not a valid win32 application
    Anyone know what causes this error and how I can correct it? Thank you.

    The third option, bad network card.
    I had the same problem over the last few days. One particular machine just would not image. Changed power supply, hard drive memtest on the ram, nothing. Failed with a PNP error before the imaging process had begun. Tried both a win8 and win7 WDS server.
    The last thing to try, was disable the onboard network and put in a bootable PCI card which luckily i had. The machine then imaged fine.
    To me, it looked like a ram error, or disk error, but don't forget the network card is an integral component for getting the data INTO the ram in the first place!

  • Drivers - Can you do both "Apply Driver Package" and "Auto Apply Device Drivers - PNP" in the same Task Seqeunce ?

    Hi All,
    It has been mentioned to be that it is possible to have both "Apply Driver Package" and "Auto Apply Device Drivers - PNP' " specified in the same task sequence, with some kind of logic specified that if the Apply Driver Package step does
    not run due to the hardware wmi query not being valid then the 'Apply Device Drivers -PNP' will run instead. Vice-versa - if the "Apply Driver Package" wmi query is correct and driver package applied then the 'Auto Apply Device Drivers -PNP'
    will not run and be skipped.
    Is this possible ?
    I can't seem to find any documentation or reference indication this can be done. :-(
    Many thanks everyone..

    To add some info here, note that the end result of both tasks is the same. Neither actually *installs* drivers in any way. Both simply copy the drivers to the target system and inject them into the image being deployed where they are then available to Windows
    Setup (which runs during the Setup Windows and ConfigMgr task) to install based upon the Windows Setup standard PNP detection.
    Thus, using both task types, depending upon what is in the driver packages and what is detected by the OSD PNP detection (which differs slightly from the OS PNP which is far more complex and has been described as a "black art"), potentially injects
    more drivers into the image potentially making more drivers available to Windows Setup. This could of course increase your deployment time.
    I've thought about this approach before and it is technically valid, but I've never had to resort to it. I've always just made sure that the drivers packages are complete. If you're trying to address the scenario of hardware without a explicit driver package,
    I could see it working but I could also see it causing problems because drivers are weird. In general, I would recommend always testing new hardware and anything not accounted for is considered unsupported.
    Jason | http://blog.configmgrftw.com | @jasonsandys

  • View data in client B from client A in the same SID without a valid logon?

    Hi Folks
    We are planning on upgrading our 4.6C system to ERP 6.0, and are initialy considering having two clients in the same sandbox SID.  One would be for the developers to perform code remediation checks (client A), and one would contain a copy of production data for performing testing of functionality over live data (client B).
    Would it be possible to view data in client B from client A in the same system without a valid logon to client B or RFC connection to client B from client A?   For example via the use on an ABAP program to SQL the database?
    I know one can use transactions like SM30/SM31 to view, compare, and adjust data between clients, but this requires an RFC connection and valid logon to the target client.
    Regards
    Kevin.

    Hi Kevin.
    >
    Kevin McLatchie wrote:
    > Would it be possible to view data in client B from client A in the same system without a valid logon to client B or RFC connection to client B from client A?   For example via the use on an ABAP program to
    Short answer: yes.
    If someone has the right to write and execute ABAP reports on the system he is able to access the data of all clients. So I don't think that this setup is advisable. Don't mix development and production data in one system.
    Best regards,
    Jan

  • DEVOLUÇÃO DE EXPORTAÇÃO - CFOP 3201 - GRC VALIDA DADOS DI.

    Boa tarde a todos!
    Estamos em um projeto de NFE XML 2.00 e nos deparamos com o seguinte erro:
    Ao emitirmos um NF-e de devolução da mercadoria que se encontrava no Porto (devolução de exportação - CFOP 3201), a validação do monitor GRC informa que é necessário constar os dados de importação, apesar deste processo não se tratar de importação. Os seguintes logs de validação são gerados:
    Erro de validação: campo Código do fabricante estrangeiro no sistema. Campo é obrigatório e não pode ficar em branco. (campo IT_NFE_ADI-CFABRICANTE, ID campo I028)
    Erro de validação: campo Nº da adição. Campo é obrigatório e não pode ficar em branco. (campo IT_NFE_ADI-NADICAO, ID campo I026)
    Erro de validação: campo Nº sequencial do artigo na adição. Campo é obrigatório e não pode ficar em branco. (campo IT_NFE_ADI-NSEQADIC, ID campo I027)
    Erro de validação: campo . Campo é obrigatório e não pode ficar em branco. (campo IT_NFE_IMP-CEXPORTADOR, ID campo I024)
    Erro de validação: campo . Campo é obrigatório e não pode ficar em branco. (campo IT_NFE_IMP-DDESEMB, ID campo I023)
    Erro de validação: campo . Campo é obrigatório e não pode ficar em branco. (campo IT_NFE_IMP-DDI, ID campo I020)
    Erro de validação: campo . Campo é obrigatório e não pode ficar em branco. (campo IT_NFE_IMP-NDI, ID campo I019)
    Erro de validação: campo . Campo é obrigatório e não pode ficar em branco. (campo IT_NFE_IMP-UFDESEMB, ID campo I022)
    Erro de validação: campo . Campo é obrigatório e não pode ficar em branco. (campo IT_NFE_IMP-XLOCDESEMB, ID campo I021)
    Estamos no SAPK-10015INSLLNFE e as seguintes notas relacionadas a validação estão aplicadas:
    1493980     Validation for field xJust in cancel and skipping messages
    1499921     Problem with validation after implementing SP15
    1500046     Upgrade validation rule for field ID for version 2.00
    1500742     Adjust validation for field NADICAO and NSEQADIC layout 2.00
    1502217     Extend validation rules for , layout 2
    1504379     Adjust validation for field X_CLISTSERV
    1511291     Update allowed values for field E1_CPAIS for validation
    1511577     Update validation rules for field VUNCOM_V20
    1520861     Update validation rules for OIL_CPRODANP and OIL_UFCONS
    Não encontrei nenhuma nota SAP recente para o componente SLL-NFE que seja relacionada a este problema.
    Desde já agradeço pela ajuda.
    Sds / Renato Penido.

    Boa tarde, Fernando,
    Obrigado pela pronta resposta.
    Debugamos a BADI e descobrimos que os dados de importação estão sendo gravado "em branco", gerando o erro de validação no GRC, tal qual dito por você.
    Aprimoramos a lógica da BADI para que a tag de importação não seja preenchida indevidamente para as notas de devolução do porto e as notas foram aprovadas.
    Muito obrigado,
    Renato Penido.

Maybe you are looking for