zoukankan      html  css  js  c++  java
  • FIForeign trade data incomplete for domestic business

    Symptom

    A billing document cannot be transferred into accounting because the foreign trade data is incomplete.
    However, the underlying business process is a domestic business!

    Additional key words

    VF01, VF02, EIPO, EIKP, foreign trade, incompleteness, domestic, delivery, billing document, EXNUM, EXPKZ,export indicator, export number

    Cause and prerequisites

    In the respective delivery or in the billing document, for domestic business you by mistake go to the foreign trade data into a field. Since the incompletion log requires at least one entry for foreign trade, you must fill one field  in order to be able to leave the foreign trade data again without canceling document processing.
    Here, an export indicator and an export number is assigned which cause the incompleteness of the whole document due to missing export data.

    Solution

    A solution in the standard system is currently not planned since because of various customer requests the foreign trade data in the delivery should be accessed and maintained for domestic business too. An example is the inbound delivery in a bonded warehouse where the forwarding agent should get information already in advance.

    To avoid incorrect billing documents, proceed as follows:
    Copy data transport routine 001 to a routine 601 and enhance the new routine according to the attached correction instruction (RV60C601). Store this new data transport routine in Customizing for the copying control for billing documents for the processes you use, for example
    - F2 - LF, item category TAN.   (delivery-related)

    If you already use an own data transport routine, in this data transport routine include the attached source code.

    You must cancel existing billing documents and then create them again.
    If you do not want to cancel existing documents, implement the attached correction (program RV60AFZZ) and release the documents either individually (VF02, default transaction) or via the list of blocked billing documents (VFX3).
    After you completed the correction, you should cancel this solution (RV60AFZZ) again.
    Also refer to the attached Note 170183.

    代码修改:
    方案一:

    R3TR PROG RV60C601

    FORM DATEN_KOPIEREN_601

    Delta 001
    Context Block
    FORM DATEN_KOPIEREN_601.
    
    * Kopfdaten
    * VBRK-xxxxx = ............
    
    

    Delete Block
     

    Insert Block
    * Prüfen Exportvorgang
      IF VBRK-LANDTX = VBRK-LAND1.
        CLEAR: VBRK-EXPKZ,
               VBRK-EXNUM.
      ENDIF.
    
     

    方法二

    R3TR PROG RV60AFZZ

    FORM USEREXIT_PRICING_PREPARE_TKOMK

    Delta 001

    Context Block
    FORM USEREXIT_PRICING_PREPARE_TKOMK.
    
    

    Delete Block
     

    Insert Block
    * Prüfen Exportvorgang
      IF XVBRK-LANDTX = XVBRK-LAND1.
        CLEAR: XVBRK-EXPKZ,
               XVBRK-EXNUM.
      ENDIF.
    

  • 相关阅读:
    爬虫那些事儿---爬虫选择策略
    爬虫那些事儿--Http返回码
    【珍藏】linux 同步IO: sync、fsync与fdatasync
    perf学习-linux自带性能分析工具
    进程调度原理
    phpmyadmin 免登陆
    请为main函数提供返回值
    悬挂else引发的问题
    PhpMyAdmin导入数据库大小限制?
    linux内核Makefile整体分析
  • 原文地址:https://www.cnblogs.com/xiaomaohai/p/6157119.html
Copyright © 2011-2022 走看看