CIF comparison/reconciliation

Hai,
          I found in the release notes for SCM 4.1 that "the CIF comparison/reconciliation of transaction data (delta report) can be checked". I also found other things like checking the CVCs and CIF data for consistency.How do these work? I understood that it checks the validity and consistency of the Master and Transaction data.  I am not completely clear with this. Can somebody explain me what it means and any transactions used for it?
Here is where I found it:
http://help.sap.com/saphelp_scm41/helpdata/en/28/b34c40cc538437e10000000a155106/frameset.htm
Page 165.
I appreciate if anyone can refer me any documentation.
Thank you.

Hi Visu,
The transaction for CIF comparison/reconciliation is /SAPAPO/CCR.
For details please see help.sap.com. At high level CIF Comparison/ reconcilitation report is used to compare the transaction (orders, stocks, PIRs) data between APO and connected R3 / ERP system. Please note timeseries data or master data is not compared.
After comparison the report displays the differences and gives you an option to reconcile the differences. You can try reconciling the differences after making sure the root cause of the differences (mostly master data problems) are taken care of.
Hope this helps.
Thanks,
Somnath

Similar Messages

  • Unable to do the (CCR in APO) comparison/reconciliation of transaction data PO and PR in APO

    Hi Gurus,
    Unable to do the (CCR in APO) comparison/reconciliation of transaction data PO and PR in APO Due to the error 181-Schedule line does not exist in APO ,Error code 182-Schedule line without external number does not exist in R/3.
    kindly suggest me ,what we need to do corrective action from ECC side and APO side.
    Regards,
    Babu

    Hi Babu,
    First make sure that order is not set with deletion flag, you can check some random orders for this.
    Steps to be followed:
    1) for all entries with error "181-Schedule line does not exist in APO" click on "Send to APO". similarly for entries with error "182-Schedule line without external number does not exist in R/3" click on "Send to R/3", most likely this type of issue get resolved with this step only, if not.
    2) Next you need to go to transaction code /n/sapapo/cq, check what all messages you are getting there. Correct the error if you are able to understand it from here i.e. rfc connection is not set, no active IM exists etc..
    3) In case you are not able to understand or correct the issue from CQ, then you need to go and check in transaction code CFG1 in ECC, and /n/sapapo/c3 in APO, check in ECC with object CIF and log class "only very important logs".
    In APO object "CIFSCM" and log class "only very important logs".
    Most probably you will be able to get exact or directional reason of the issue.
    Hope this helps.
    Rgds
    Sourabh

  • CCR - Execute Comparison/Reconciliation not allowing to delete ECC orders

    SNP Purchase Requisitions were created in APO as part of CTM solve and transferred to ECC. Some of these Purchase requisitions were not deleted in ECC even though it was deleted in APO. CCR (reconciliation program) shows up these Purchase requisitions as available in ECC and not in APO and only give an option to transfer to APO. Why am I not able to delete these orders (available in ECC not in APO) using CCR? The delete button just donu2019t become active.

    Followed up with SAP development team. As per development team functionality to delete PO's or Purchase req in R/3  that are not in APO is not supported at all by deltareport (CCR Report in SCM). CCR report only allows to send PO or Purchase req (missing in APO) to APO.
    However a customer specific enhancment can be made to program  /SAPAPO/CIF_DELTA3_INCFORM to activate the delete Button
    FORM create_errcat_configs :
    ls_errcat_configs-typ = gc_objtyp-t_prq.
    ls_errcat_configs-buttons = '10000'. --> change to '10010'
    This form is used for setting the configuration of the buttons for each objecttype-err_category - combination. The settings are stored in the table GT_ERRCAT_CONFIGS. The meanings of the settings are:  
      '1'  =  button on                                                  
      '0'  =  button off                                                 
      example: '011' means button1=off, button2=on, button3=on.                                                                               
    Error_categories:                                                  
      A = missing in APO                                                 
      B = missing in R/3 without ext.key                                 
      C = missing in R/3 with    ext.key                                 
      D = differences in content                                         
      E = not in active integration model                                
      F = too much in APO                                                
      G = differencies in io-nodes                                       
      H = differencies in operations                                     
      I = differencies in downtimes                                      
      S = stock not in R/3 -> delete in APO                              
      T = duplicate stock in APO -> delete and resend                    
      U = different quantities in R/3 and APO -> resend                                                                               
    Buttons:                                                           
      1.Button = send to APO                                             
      2.Button = send to R/3                                             
      3.Button = delete in APO                                           
      4.Button = delete in R/3
    Edited by: Allen Thomas on Sep 2, 2010 6:29 AM

  • CIF -DeltaReport  error 183 schedule line does not exist in R/3

    Hi Expert,
    In the delta report (/SAPAPO/CCR - CIF_DELTAREPORT), there are discrepancies that say error code 183, which is Schedule line does not exist in R/3..
    But when we look in R3, they are actually there. So we don’t want these showing as a discrep in the delta report.
    Example in ‘purchasing’, ‘confirmations’, ‘missing in R3 with external key’
    If you run DELTAREPORT for  purchasing, confirmation, unjustified error 183 are displayed despite of no inconsistency really exists.
    Please help why these dscrepancies displayed.
    we are running on SCM510.

    Hello Maddy
    Please go through below SAP notes - 
    1131469 - DELTAREPORT: unjustified error 181/183 for confirmation
    794281 - Locked purchase orders missing from R/3
    1022343 - Delta report displays too many errors (181)
    817354 - No delete event when you delete orders in APO
    Some Old SCN threads -
    CCR Error 154 - Planned Order Missing in R3 wit... | SCN
    CIF Problem -- Purchase Orders - Missing in R/3 with External Key
    This is good document on CCR error handling.
    CIF-Comparison / Reconciliation of Transaction Data
    Hope this will help.
    Thank you
    Satish Waghmare

  • Run time error

    Dear All,
    During the transaction /n/sapapo/ccr (Reconsilation of transaction data) in client SCP 950, system displays the run time error which are attached herewith.
    This is the activity a used to execute regularly (Daily) and first time i recieved this message - -
    Runtime Errors         ASSERTION_FAILED                                                            
    Date and Time          13.07.2007 10:13:37                                                         
    ShrtText                                                                               
    The ASSERT condition has been violated.                                                       
    What happened?                                                                               
    In the current application program, the system recognized a situation                         
        involving the ASSERT statement that should not occur. A runtime error                         
        occurred, either because there was no activation ID entered or because                        
        the ID of the activation mode used was set to "Cancel.                                        
    What can you do?                                                                               
    Print out the error message (using the "Print" function)                                      
        and make a note of the actions and input that caused the                                      
        error.                                                                               
    To resolve the problem, contact your SAP system administrator.                                
        You can use transaction ST22 (ABAP Dump Analysis) to view and administer                      
         termination messages, especially those beyond their normal deletion                          
        date.                                                                               
    is especially useful if you want to keep a particular message.                                                                               
    Error analysis                                                                               
    The following activation ID was used: "No checkpoint group specified"                                                                               
    If the FIELDS addition was used with this ASSERT statement, the content                       
        of the first 8 fields is as follows:                                                          
        " (not used) "                                                                               
    " (not used) "                                                                               
    " (not used) "                                                                               
    " (not used) "                                                                               
    " (not used) "                                                                               
    " (not used) "                                                                               
    " (not used) "                                                                               
    " (not used) "                                                                               
    How to correct the error                                                                               
    Probably the only way to eliminate the error is to correct the program.                                                                               
    You may able to find an interim solution to the problem                                       
        in the SAP note system. If you have access to the note system yourself,                       
        use the following search criteria:                                                                               
    "ASSERTION_FAILED" C                                                                               
    "/SAPAPO/SAPLTIMESTAMP" or "/SAPAPO/LTIMESTAMPU08"                                            
        "/SAPAPO/TIMESTAMP_DIFFERENCE"                                                                
        If you cannot solve the problem yourself and you wish to send                                 
        an error message to SAP, include the following documents:                                                                               
    1. A printout of the problem description (short dump)                                         
           To obtain this, select in the current display "System->List->                              
           Save->Local File (unconverted)".                                                                               
    2. A suitable printout of the system log                                                      
           To obtain this, call the system log through transaction SM21.                              
           Limit the time interval to 10 minutes before and 5 minutes                                 
           after the short dump. In the display, then select the function                             
           "System->List->Save->Local File (unconverted)".                                                                               
    3. If the programs are your own programs or modified SAP programs,                            
           supply the source code.                                                                    
           To do this, select the Editor function "Further Utilities->                                
           Upload/Download->Download".                                                                               
    4. Details regarding the conditions under which the error occurred                            
           or which actions and input led to the error.                                               
    System environment                                                                               
    SAP Release.............. "640"                                                                               
    Application server....... "scmprd"                                                            
        Network address.......... "172.16.10.47"                                                      
        Operating system......... "AIX"                                                               
        Release.................. "5.3"                                                               
        Hardware type............ "0002BFAAD700"                                                      
        Character length......... 16 Bits                                                             
        Pointer length........... 64 Bits                                                             
        Work process number...... 0                                                                   
        Short dump setting....... "full"                                                                               
    Database server.......... "scmprd"                                                            
        Database type............ "ORACLE"                                                            
        Database name............ "SCP"                                                               
        Database owner........... "SAPSCP"                                                                               
    Character set............ "C"                                                                               
    SAP kernel............... "640"                                                               
        Created on............... "Jan 18 2006 20:47:39"                                              
        Created in............... "AIX 1 5 00538A4A4C00"                                              
        Database version......... "OCI_920 "                                                                               
    Patch level.............. "109"                                                               
        Patch text............... " "                                                                               
    Supported environment....                                                                     
        Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE                        
         10.2.0.."                                                                               
    SAP database version..... "640"                                                               
        Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"                                                                               
    Memory usage.............                                                                     
        Roll..................... 16192                                                               
        EM....................... 196923232                                                           
        Heap..................... 0                                                                   
        Page..................... 98304                                                               
        MM Used.................. 186636840                                                           
        MM Free.................. 1895288                                                             
        SAP Release.............. "640"                                                                               
    User and Transaction                                                                               
    Client.............. 950                                                                      
        User................ "SCMATP"                                                                 
        Language key........ "E"                                                                      
        Transaction......... "/SAPAPO/CCR "                                                           
        Program............. "/SAPAPO/SAPLTIMESTAMP"                                                  
        Screen.............. "SAPMSSY0 1000"                                                          
        Screen line......... 6                                                                        
    Information on where terminated                                                                   
        The termination occurred in the ABAP program "/SAPAPO/SAPLTIMESTAMP" in                       
         "/SAPAPO/TIMESTAMP_DIFFERENCE".                                                              
        The main program was "/SAPAPO/CIF_DELTAREPORT3 ".                                                                               
    The termination occurred in line 61 of the source code of the (Include)                       
         program "/SAPAPO/LTIMESTAMPU08"                                                              
        of the source code of program "/SAPAPO/LTIMESTAMPU08" (when calling the editor                
         610).                                                                               
    Source Code Extract                                                                               
    Line  SourceCde                                                                               
    31     lv_time_int_low      TYPE i,                                                            
       32     lv_timediff_int      TYPE i,                                                            
       33     lv_datediff_int      TYPE i,                                                            
       34     lv_time              TYPE t,                                                            
       35     ls_time              TYPE tstr_timestr.                                                 
       36                                                                               
    37 * check timestamp parameter                                                                 
       38 * ASSERT NOT iv_timestamp_high IS INITIAL.                                                  
       39 * ASSERT NOT iv_timestamp_low  IS INITIAL.                                                  
       40 * ASSERT iv_timestamp_low <= iv_timestamp_high.                                             
       41   IF iv_timestamp_high IS INITIAL                                                           
       42   OR iv_timestamp_low  IS INITIAL.                                                          
       43     RAISE invalid_parameter.                                                                
       44   ENDIF.                                                                               
    45   IF iv_timestamp_high < iv_timestamp_low.                                                  
       46     RAISE invalid_parameter.                                                                
       47   ENDIF.                                                                               
    48                                                                               
    49 * prepare timestamps                                                                        
       50 * .. split into date and time integers                                                      
       51   ls_timestamp_high = iv_timestamp_high.                                                    
       52   lv_date_int_high  = ls_timestamp_high-date.                                               
       53   lv_time_int_high  = ls_timestamp_high-time.                                               
       54   ls_timestamp_low  = iv_timestamp_low.                                                     
       55   lv_date_int_low   = ls_timestamp_low-date.                                                
       56   lv_time_int_low   = ls_timestamp_low-time.                                                
       57                                                                               
    58 * .. calc date diff                                                                         
       59 * .. check against max. allowed integer difference                                          
       60   lv_datediff_int = lv_date_int_high - lv_date_int_low.                                     
    >>>>>   ASSERT lv_datediff_int <= lc_datediff_intmax.                                             
       62                                                                               
    63 * calc time diff                                                                               
    64   lv_timediff_int = lv_time_int_high - lv_time_int_low.                                     
       65   IF lv_timediff_int < 0.                                                                   
       66     ADD 86400 TO lv_timediff_int.                                                           
       67     SUBTRACT 1 FROM lv_datediff_int.                                                        
       68   ENDIF.                                                                               
    69                                                                               
    70 * calc total duration                                                                       
       71   lv_duration_int = lv_datediff_int * 86400 + lv_timediff_int.                              
       72   lv_time = lv_timediff_int.                                                                
       73   ls_time = lv_time.                                                                        
       74   ls_duration-hours   = lv_duration_int DIV 3600.                                           
       75   ls_duration-minutes = ls_time-minute.                                                     
       76   ls_duration-seconds = ls_time-second.                                                     
       77                                                                               
    78   ev_duration_packed  = ls_duration.                                                        
       79   ev_duration_integer = lv_duration_int.                                                    
       80 ENDFUNCTION.                                                                               
    Contents of system fields                                                                         
    Name     Val.                                                                               
    SY-SUBRC 0                                                                               
    SY-INDEX 0                                                                               
    SY-TABIX 1                                                                               
    SY-DBCNT 1                                                                               
    SY-FDPOS 6                                                                               
    SY-LSIND 0                                                                               
    SY-PAGNO 0                                                                               
    SY-LINNO 1                                                                               
    SY-COLNO 1                                                                               
    SY-PFKEY                                                                               
    SY-UCOMM                                                                               
    SY-TITLE CIF - Comparison/Reconciliation of Transaction Data                                      
    SY-MSGTY                                                                               
    SY-MSGID                                                                               
    SY-MSGNO 000                                                                               
    SY-MSGV1                                                                               
    SY-MSGV2                                                                               
    SY-MSGV3                                                                               
    SY-MSGV4                                                                               
    Active Calls/Events                                                                               
    No.   Ty.          Program                             Include                             Line   
          Name                                                                               
    5 FUNCTION     /SAPAPO/SAPLTIMESTAMP               /SAPAPO/LTIMESTAMPU08                  61  
          /SAPAPO/TIMESTAMP_DIFFERENCE                                                                
        4 FORM         /SAPAPO/SAPLCIF_DELTA3              /SAPAPO/LCIF_DELTA3F17                349  
          COMPARE_ORDER_HEADER                                                                        
        3 FUNCTION     /SAPAPO/SAPLCIF_DELTA3              /SAPAPO/LCIF_DELTA3U03                125  
          /SAPAPO/CIF_DELTA3_COMP_ORDER                                                               
        2 FUNCTION     /SAPAPO/SAPLCIF_DELTA3              /SAPAPO/LCIF_DELTA3U01                871  
          /SAPAPO/CIF_DELTA3_COMP                                                                     
        1 EVENT        /SAPAPO/CIF_DELTAREPORT3            /SAPAPO/CIF_DELTAREPORT3              189  
          START-OF-SELECTION                                                                          
    Chosen variables                                                                               
    Name                                                                               
    Val.                                                                               
    No.       5 Ty.          FUNCTION                                                                 
    Name  /SAPAPO/TIMESTAMP_DIFFERENCE                                                                
    IV_TIMESTAMP_HIGH                                                                               
    #q1###                                                                               
    02073899                                                                               
    2001125C                                                                               
    IV_TIMESTAMP_LOW                                                                               
    ##q!####                                                                               
    00720899                                                                               
    2011125C                                                                               
    EV_DURATION_INTEGER                                                                               
    0                                                                               
    0000                                                                               
    0000                                                                               
    EV_DURATION_PACKED                                                                               
    000000                                                                               
    00000C                                                                               
    SYST-REPID                                                                               
    /SAPAPO/SAPLTIMESTAMP                                                                         
        0000000000000000000000000000000000000000                                                      
        0000000000000000000000000000000000000000                                                      
        2545454254545444554452222222222222222222                                                      
        F31010FF310C49D5341D00000000000000000000                                                      
    %_SPACE                                                                               
    0                                                                               
    0                                                                               
    2                                                                               
    0                                                                               
    LS_TIMESTAMP_HIGH                                                                               
    22000713182959                                                                               
    00000000000000                                                                               
    00000000000000                                                                               
    33333333333333                                                                               
    22000713182959                                                                               
    LV_DATE_INT_HIGH                                                                               
    803363                                                                               
    0042                                                                               
    0C23                                                                               
    LS_TIMESTAMP_HIGH-DATE                                                                               
    22000713                                                                               
    00000000                                                                               
    00000000                                                                               
    33333333                                                                               
    22000713                                                                               
    LV_TIME_INT_HIGH                                                                               
    66599                                                                               
    0002                                                                               
    0147                                                                               
    LS_TIMESTAMP_HIGH-TIME                                                                               
    182959                                                                               
    000000                                                                               
    000000                                                                               
    333333                                                                               
    182959                                                                               
    LS_TIMESTAMP_LOW                                                                               
    20071210182959                                                                               
    00000000000000                                                                               
    00000000000000                                                                               
    33333333333333                                                                               
    20071210182959                                                                               
    LV_DATE_INT_LOW                                                                               
    733021                                                                               
    0025                                                                               
    0BFD                                                                               
    LS_TIMESTAMP_LOW-DATE                                                                               
    20071210                                                                               
    00000000                                                                               
    00000000                                                                               
    33333333                                                                               
    20071210                                                                               
    LV_TIME_INT_LOW                                                                               
    66599                                                                               
    0002                                                                               
    0147                                                                               
    LS_TIMESTAMP_LOW-TIME                                                                               
    182959                                                                               
    000000                                                                               
    000000                                                                               
    333333                                                                               
    182959                                                                               
    SY-UNAME                                                                               
    SCMATP                                                                               
    000000000000                                                                               
    000000000000                                                                               
    544455222222                                                                               
    33D140000000                                                                               
    SCREEN-INPUT                                                                               
    1                                                                               
    0                                                                               
    0                                                                               
    3                                                                               
    1                                                                               
    LV_DATEDIFF_INT                                                                               
    70342                                                                               
    001C                                                                               
    0126                                                                               
    LV_TIMEDIFF_INT                                                                               
    0                                                                               
    0000                                                                               
    0000                                                                               
    SYST                                                                               
    #######################################&#332;###############################################&#19800; C#&#1280;##
        0000000000000000000000000000000000000000000000000000000000000000000000000000000000000004000000
        000000000000000000000000000000000000000100000000000000000000000000000000000000000000000D000500
        0000000000000000000000000000000800000004000000000000000000000000000000000000010900000005240000
        0000010200000000000001060100010C0000000C0000000002000000000000000000000000000B000001000803000C
    SY-REPID                                                                               
    /SAPAPO/SAPLTIMESTAMP                                                                         
        0000000000000000000000000000000000000000                                                      
        0000000000000000000000000000000000000000                                                      
        2545454254545444554452222222222222222222                                                      
        F31010FF310C49D5341D00000000000000000000                                                      
    %_DUMMY$$                                                                               
    0000                                                                               
    0000                                                                               
    2222                                                                               
    0000                                                                               
    No.       4 Ty.          FORM                                                                     
    Name  COMPARE_ORDER_HEADER                                                                        
    SYST-REPID                                                                               
    /SAPAPO/SAPLCIF_DELTA3                                                                        
        0000000000000000000000000000000000000000                                                      
        0000000000000000000000000000000000000000                                                      
        2545454254544445444543222222222222222222                                                      
        F31010FF310C396F45C413000000000000000000                                                      
    GC_APPEND_MODE                                                                               
    3                                                                               
    0                                                                               
    0                                                                               
    3                                                                               
    3                                                                               
    LS_FIELDS_TO_COMPARE-DUEDATE                                                                      
        X                                                                               
    0                                                                               
    0                                                                               
    5                                                                               
    8                                                                               
    SYST                                                                               
    #######################################&#332;###############################################&#19800; C#&#1280;##
        0000000000000000000000000000000000000000000000000000000000000000000000000000000000000004000000
        000000000000000000000000000000000000000100000000000000000000000000000000000000000000000D000500
        0000000000000000000000000000000800000004000000000000000000000000000000000000010900000005240000
        0000010200000000000001060100010C0000000C0000000002000000000000000000000000000B000001000803000C
    LS_APO_ORDER-ORDTYPE                                                                               
    5                                                                               
    0                                                                               
    0                                                                               
    3                                                                               
    5                                                                               
    GC_PLANNED_ORDER                                                                               
    5                                                                               
    0                                                                               
    0                                                                               
    3                                                                               
    5                                                                               
    LS_R3_ORDER-STATUSCNF                                                                               
    0                                                                               
    0                                                                               
    2                                                                               
    0                                                                               
    GC_ORDER_STATUS_NO_CONF                                                                               
    1                                                                               
    0                                                                               
    0                                                                               
    3                                                                               
    1                                                                               
    LS_APO_ORDER-STATUSCNF                                                                               
    0                                                                               
    0                                                                               
    2                                                                               
    0                                                                               
    GC_PRED_OUT_DEL                                                                               
    A                                                                               
    0                                                                               
    0                                                                               
    4                                                                               
    1                                                                               
    GC_TND_DELETE                                                                               
    CN                                                                               
    00                                                                               
    00                                                                               
    44                                                                               
    3E                                                

    Dear Sajit,
    Go through the following OSS Notes:
    <a href="https://websmp110.sap-ag.de/form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=901957&_NLANG=E">901957</a>, <a href="https://websmp110.sap-ag.de/form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1036880&_NLANG=E">1036880</a>, <a href="https://websmp110.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1067414&_NLANG=E">1067414</a>
    Regards,
    Naveen.

  • Max-stack-size - default_stksize

    Hi,
    First, sorry for my english ^^
    I'm new on Solaris. I installed Solaris 10 on Sun V490 . I use Core Network.
    Why with the default setting, daemons or process of the OS "don't work" like this:
    Jun 17 14:50:10 unknown genunix: [ID 883052 kern.notice] basic rctl process.max-stack-size (value 8683520) exceeded by process 353In this example I generate the error with the format command. But I get this error with other command or deamon like nscd.
    I had the same problem with the value max-file-descriptor. The values set by projmod for the system project did not seem take effect. Thus I used the "old" parameters rlim_fd_cur, rlim_fd_max. Now it's ok.
    I find this parameter default_stksize in the Sun documentation. I put this in my /etc/system file:
    set default_stksize=16384At the boot time I have no error message for the value, but the max-stack-size value is the same:
    prctl -n process.max-stack-size 130
    process: 130: /usr/sbin/nscd
    NAME PRIVILEGE VALUE FLAG ACTION RECIPIENT
    process.max-stack-size
    basic 8,28MB - deny 130
    privileged 127MB - deny -
    system 2,00GB max deny -
    nscd is in the system project:
    ps -p 130 -o project
    PROJECT
    system
    Thank in advance, any idea is welcome.
    Guillaume

    Hi Prasad,
    Block Size is the number of parallel processes that are being executed in background during the application.  This is normally a configuration activity to be configured in line with basis.
    In Block size, we enter the number of objects to be processed per block by the CIF comparison/reconciliation during data selection in SAP APO or in the partner system.
    If you increase the block size, the memory required also increases. This has a positive effect on performance. If processes are cancelled due to lack of memory, you can decrease the block size to save memory.
    If you do not enter anything here, the system determines the block size dynamically from the number of objects that actually exist and the maximum number of work processes available.
    Normally, when you execute a job in background, it picks up the application server automatically or by manually defined server.  In parallel processing, at a time, one or more job of the same identify can be triggered under this scenario by defining application servers.  But too many parallel processing activity will affect the performance.
    One needs to define the parallel processes also to control system behaviour.  The Parallel processing profile is defined for parallel processing of background jobs. You then assign these profiles to variants in the applications.
    Regards
    R. Senthil Mareeswaran.

  • Min, Max Block Size, Default Blocksize ??

    Hi All,
    Can any one please explain me the exact meaning of the Min Block size, Max Blocksize that we maintain under the "Block size for DP/SNP Parallel Processing Profile ".
    Please let me know the application of the same. Why do we maintain this setting ???
    What does it mean by a BLOCK SIZE ???
    Any input on the same is highly appreciated.
    Thanks in Advance,
    Prasad.

    Hi Prasad,
    Block Size is the number of parallel processes that are being executed in background during the application.  This is normally a configuration activity to be configured in line with basis.
    In Block size, we enter the number of objects to be processed per block by the CIF comparison/reconciliation during data selection in SAP APO or in the partner system.
    If you increase the block size, the memory required also increases. This has a positive effect on performance. If processes are cancelled due to lack of memory, you can decrease the block size to save memory.
    If you do not enter anything here, the system determines the block size dynamically from the number of objects that actually exist and the maximum number of work processes available.
    Normally, when you execute a job in background, it picks up the application server automatically or by manually defined server.  In parallel processing, at a time, one or more job of the same identify can be triggered under this scenario by defining application servers.  But too many parallel processing activity will affect the performance.
    One needs to define the parallel processes also to control system behaviour.  The Parallel processing profile is defined for parallel processing of background jobs. You then assign these profiles to variants in the applications.
    Regards
    R. Senthil Mareeswaran.

  • Sales Orders transfer using CIF

    Hi,
    We are having a rather peculiar situation in our project where Sales orders do not get CIFfed across to APO. The suspicion that it could be due to a RFC issue seems to be pretty slim, considering the fact that Product and Locations are getting CIFfed across properly. When the integration model is activated there is a clear message however that the sales order is transmitted. But same is not seen using the CIF comparison report /SAPAPO/CCR.
    Have any of you guys observed a situation like this?
    Thanks much,
    Srikanth

    Srikanth,
    we are not able to access the inbound queue of APO using the button still.
    QRFC monitor is the equivalent of SMQ1.  You can review, delete, or reprocess outbound queues, or individual Logical Unit of Work (LUWs)  here.  In R/3, generally, you cannot repair any APO queues, such as the APO inbound.  For this, you must log onto APO.
    When you click 'ignore', the error is ignored and the next LUW is processed.  If there are no futher errors, or if you press ignore repeatedly, you will eventually process every possible LUW in the queue.  The errored LUWs remain in the queue, unprocessed, with an error status, and the final queue event is never reached.  Without the final event the IM will not be activated
    There are 4 possible queues. 1.  R/3 outbound and optionally 2. APO inbound; 3. APO outbound and optionally 4. R/3 inbound.
    Using SMQ1 and SMQ2 in R/3 you can only manage the R/3 queues (r/3 outbound and r/3 inbound).  If you wish to repair or delete the APO outbound or inbound, you must log ont APO and use SMQ1 (outbound) and SMQ2 (inbound).  Most people I know just use /SAPAPO/CQ, where, assuming proper authorization is set up, it can be configured to both review and edit all four queues in one transaction.
    Now you say you cannot get new orders to go across without Deactivate/reactivate.  This implies that the IM is not configured properly for real time replication.  Did you read the connectivity and replication guides I mentioned earlier?  Specifically the section about "Activating the Application Indicator" (BF11)?
    Regards,
    DB49

  • User exit CIFMAT01

    Dear All,
    We are facing problems while using the CIF user exit CIFMAT01.
    We have written a code to select the materials based on certain criteria. However when we acttivate the integration model the CIF user exit is not getting called.
    Is there any global setting through which user exits need to be enabled for CIF?
    regards,
    Kedar

    Hello Kedar,
    I suppose the comments I have added to this user-exit in our connected R/3 systems might help you:
    OSS 828026: This user-exit is called up to three times during
                data transfer to a SCM system.
                Parameter IV_MAP_STATUS shows for which functionality
                the current call is made.
    '1': New material master data is mapped to analyze SCM-relevant changes into the SCM format
    '2': Old material master data is mapped to analyze SCM-relevant changes into the SCM format
    '3': New material master data is mapped for the CIF transfer
    '4': Location products for MRP areas are transferred
    '5': Material master data is mapped for the CIF comparison and reconciliation report.
    Remarks:
    - the target destination is not maintained in status '1' or '2'
    - the call with status '3' is done in an update task if immediate transfer
        is executed when changing a product. In this case it is not
        possible to debug this call. If necessary CFM2, CFP1 or RIMODINI
        have to be used for debugging.
    Regards.
    Hubert

  • SAPAPO/RRP3 vs MD04

    Hello Guru,
    i would like to ask about the category i have check SAPAPO/RRP3, the category DEP:PReq values was not available in MD04 for a material and plant. what is the reason behind this? and what is DEP:PReq?
    SAPAPO/RRP3 category PurRqs was available in MD04 PlOrd.
    Please help me on this.
    Thanks

    Hi
    I will suggest to execute /SAPAPO/CCR - Execute Comparison/Reconciliation report for the same product and check if you have issue between ECC and APO. It will be nice you also cross check your CIF Integration models. 
    Are you using APO Deployment functionality. The DEP: PReq, i.e. Deployment: Purchase requisition which means you have confirmed these PRs. Even its category has DEP: PReq, in APO we should have sub sequent MRP element as PurRqs in MD04.
    Regarding SAPAPO/RRP3 category PurRqs was available in MD04 PlOrd. , I think it is incorrect can you please cross check the same.
    Thanks
    Amol

  • Reconciliation to verify data in R/3  and BW

    Hi Experts,
    Can any one explain me how we will maintain reconciliation to verify the data in SAP R/3 and SAP BW are same or not after the data loads. Please explain all the sources that we have.
    Thanks in advance
    Mallik

    For Unit Test, you don't need to reconcile all the records. So, I take a couple of selections. Using these, go to RSA3 in R/3 and extract the data and take sub-totals in Excel.
    Now, go to Info Provider in BW, and using same selections, download the data in BW or BEx and take sub-totals again and compare both.
    If the extractor is generic extractor based on View/Tables, you can go one additional step and get data from SE16 in R/3 to make sure RSA3 and Tables also match.
    For Business Content extractor, its a little difficult is do this step because most of them are Function Modules.
    This should be enough as long as your selections are good.
    You can compare the data from RSA3. Run RSA3 and save the data in a file and then compare with BW.
    You can compare the PSA data with R/3 to check whether your data transport is correct.But it’s very much important the end result (with data in Data Targets ex.Infocube...) should be reconciled with the R/3 data to check your update and transfer rules are working fine.
    The second part is too tricky since you cannot directly compare the reports while the formats and grouping are different.
    You can execute the reports in R/3 and apply the Update and transfer conversions (at least for random records) then reconcile with the BW data.
    Take a look on the note: 543188
    "How to Reconcile Data Between SAP Source Systems and SAP NetWeaver BI"
    The Data Reconciliation procedure is still in the SAP action item for the future release.
    But we can reconcile the data by extracting the reports and compare with the query output in Excel sheet.
    Please check for a tool "Excel Compare" in google which is really useful in comparing excel files.
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/7a5ee147-0501-0010-0a9d-f7abcba36b14
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/biw/how%20to%20validate%20infocube%20data%20by%20comparing%20it%20with%20psa%20data
    By this method you can compare your infocube data with PSA ones...clearly, every changes in R/3 (due to user exit or, above all, BW-specific standard logic) is not taken into account...if you want to consider also this part (back-end), there is no std method and it depends from every specific flow!
    also check in service.sap.com/bi
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/7a5ee147-0501-0010-0a9d-f7abcba36b14
    One way is to define Remote Cube on the R3 data source and create multiprovider on BW with the Remote Cube and the BW target. Subtract the KF on R3 from the KF in BW - anything not 0 becomes an exception.
    Sometimes the source on R3 is not as straight forward and we have had ABAP developers create summary table on R3 to compare to BW.
    Actually one to one Data comparison between R/3 and BW is done during Integration Test phase. During this time we need to sit with R/3 team and work closely because they know exactly the numbers in R/3 side and which tables Data resides and all. After loading Data same data in to BW we compare the numbers between R/3 BW. If both the teams feel there is some data missing then we start the analysis. As a first stem we will see in the extractor’s then BW side during transformation like transfer and update rules.
    Pleases see this document for more help
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/968dab90-0201-0010-c093-9d2a326969f1
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/biw/how%20to%20validate%20infocube%20data%20by%20comparing%20it%20with%20psa%20data
    verifying the data which is coming from R/3 to BW system. That is called as Reconciliation.
    That process is done with “ v lookup “functionality.
    Hope this helps and assihn points, if so
    Regards
    Raja

  • Data Reconciliation Data Sources in Business Content

    Can you tell me where we can find these data sources and explain me how to use them? Do we need to define infocube/ods or anything like that to load the data and use report to see the results?
    Please explain me with one complete scenario.
    Thanks.

    Data Reconciliation for data sources allows you to ensure the consistency of data has been loaded in to BI is available and used productively there.
    It is based on comparision of the data loaded in to BI and the application data in the source system.You can access the data in the source system directly to perform this comparison.
    The term Data Reconciliation data source is used for Data sources that are used as a reference for accessing the application data in the source directly and there fore allow you to draw comparison to the source data.
    It allows you to check the integrity of the loaded data by for EXAMPLE,comparing the total of a keyfigure in the data store object with the corresponding totals that the virtual providers access directly in the Source system.
    Hope it will helps you.....

  • Data reconciliation

    BI Experts - I am using BI as my data repository to move data from R/3 to BPC. Any suggestions on what I need to look out for? Thanks.

    Purpose
    An important aspect in ensuring the quality of data in BI is the consistency of the data.  As a data warehouse, BI integrates and transforms data and stores it so that it is made available for analysis and interpretation. The consistency of the data between the various process steps has to be ensured. Data reconciliation for DataSources allows you to ensure the consistency of data that has been loaded into BI and is available and used productively there. You use the scenarios that are described below to validate the loaded data. Data reconciliation is based on a comparison of the data loaded into BI and the application data in the source system. You can access the data in the source system directly to perform this comparison.
    The term productive DataSource is used for DataSources that are used for data transfer in the productive operation of BI. The term data reconciliation DataSource is used for DataSources that are used as a reference for accessing the application data in the source directly and therefore allow you to draw comparisons to the source data. 
    You can use the process for transaction data. Limitations apply when you use the process for master data because, in this case, you cannot total key figures, for example.
    Model
    The following graphic shows the data model for reconciling application data and loaded data:
    The productive DataSource uses data transfer to deliver the data that is to be validated to BI. The transformation connects the DataSource fields with the InfoObject of a DataStore object that has been created for data reconciliation, by means of a direct assignment.  The data reconciliation DataSource allows a VirtualProvider direct access to the application data.  In a MultiProvider, the data from the DataStore object is combined with the data that has been read directly. In a query that is defined on the basis of a MultiProvider, the loaded data can be compared with the application data in the source system.
    In order to automate data reconciliation, we recommend that you define exceptions in the query that proactively signal that differences exist between the productive data in BI and the reconciliation data in the source. You can use information broadcasting to distribute the results of data reconciliation by email, for example.
    Edited by: prem casanova on Oct 21, 2008 11:15 AM

  • KE24 Report comparison with FI GL account balance report

    Hi Friends,
    I'm comparing KE24 transaction code COPA actual line item balance with FI GL account balance report, but I'm not able to match it/not sure how to match it.
    Could you please let me know how to compare these two reports mainly to know whether all the balances in FI are moving to COPA properly. Also please let me know how the values are being extracted for this KE24 transaction code.
    Thanks & Regards,
    Dwarak

    This comparison can only be done with a thorough knowledge of the config that was made to transfer information into the COPA system. It is COMPLETELY implementation specific. It generally is grouped into several areas - Revenue, Cost of goods sold @standard, cost of goods sold period based adjustments (E.g. variances) and overheads.
    Here is some VERY broad guidelines:
    Revenue method will depend on whether you are using "vanilla" sales of inventory from SD, or whether you use resource related billing in PS. Further you will need to know which condition types post to which GL Accounts, and to which value fields.
    Cogs method will depend on the sames differences, also whether you are using material master price (VPRS), or whether you are using standard cost estimate. If you are using standard cost estimate, you need to know the cost components used, and which value fields they post to.You also need to know which GL account(s) is posted to. This is based on the valuation class in table 30. Alternatively, for resource related billing you have to know how the DIP profile was set up.
    You need to know how your production variances are posted, your purchase price variances and your overhead variances on production cost centres.
    Overheads can be posted directly from FI, from MM, or settled from an internal order or project. Alternatively, they are assessed from cost centres, to PA using assessment rules.
    You also need to know whether there are any statistical value fields, which should be excluded from the reconciliation.

  • Automatic CIF Delta Report Execution

    Hi All,
    Is it possible to directly execute the results of the of the CIF Delta report i.e.with a background job.
    Thanks
    Sachin

    Dear Ken,
    Please see the original message by SACHIN
    " Is there a way to execute the results of the CCR report"
    From what I understood , he is asking about execution of the results or in other words, the corection methods which the system proposes.. The answer is NO...
    If he had asked -" Is there a way to execute the CCR in background". The answer would have been YES.
    If you read carefully the HELP CONTENT in your post, it says only the <b>execution</b> or <i>iteration</i> or the <b>results of the comparison</b> which all the mean the same--the results when you run the COMAPARE AND RECONCILE REPORT using /sapapo/ccr
    <b>The Correction part, is manual.</b>
    I run this report everyday in the morning along with OM17 and we could not figure a way of correcting the results of the comparision in the background because SAP hasnt provided one.
    Let me give you 2 examples and I will let you decide whether this is really possible
    Say after running the CCR, we have the following 2 inconsistencies
    (1) Missing in APO-- and the correction which the system has suggested is " SEND to APO"
    (2) Missing in R3--and the correction which the system suggested is " DELETE in APO"
    There can be many different error codes and correction methods suggested by the system in a single run*
    Now tell me if there was a way for background, how will the system know which correction method to select..
    This is the reason SAP has not given any background corerction for CCR as well as OM17...
    Kindly run the report and see for yourself and let me know If you have any questions.
    Regards
    Kumar Ayyagari
    Message was edited by:
            Kumar P Ayyagari

Maybe you are looking for

  • Standard Report with Condition Type and Condition Records

    Hello to all, Is there any standard report available in which Condition Type and Condition values are displayed in either column or row format? The selection criteria can be either Quotation, Contract, Sales Order, Delivery, Invoice or Billing. Thank

  • Flash Player and the PowerBook G4

    Has anyone with a PowerBook G4, 1GHz powerPC ever had to download Version: 9,0,28,0 
Platform: Mac OS X 
Browser: Firefox, Mozilla, Netscape, AOL, Opera, and Safari
Date Posted: 11/14/2006 
Language: English "Macromedia - Flash Player" has content of

  • Error: 12705 Cannot access NLS data

    I have just downloaded and installed 11.2 Express Edition + Oracle SQL developer on Windows 7 but when I tried to connect it returned me an error: 12705 Cannot access NLS data. I tried to change NLS_LANG param in registry & skipped NLS settings bit i

  • Order of free characteristics in standard webtemplate

    Hi Gurus, i created a query with query designer. In Excel anything is fine. Also the order of the free characteristics in the navigation panel on the left side is as defined in query. But if i start the query in web i got a problem. In web the order

  • "TCP Server inactive" error in LabView 7.0

    My TCP functionality in LabView 7.0 is gone. In right bottom corner of LabView about splash it states "TCP server inactive". How do I fix this? Thanks Solved! Go to Solution.