Runtime Error every 3mins - SAPLBP_CENTRAL_PERSON or SWWDHEX

Question

HI,
I hope somebody can help me here, here's my problem:
When i checked the list of Runtime Errors (ST22), i found out that there is a RAISE_EXCEPTION error that occurs every 3 minutes. It started last week, though we didnt schedule any background jobs or change anything in the system.
Here are the Runtime Error details:
Username: WF-BATCH
Name of Runtime Error: RAISE_EXCEPTION
Short text
    Exception condition "NO_ID" raised.
What happened?
    The current ABAP/4 program encountered an unexpected     situation.
Error analysis
    A RAISE statement in the program "SAPLBP_CENTRAL_PERSON" raised the exception
    condition "NO_ID".
    Since the exception was not intercepted by a superior  program, processing was terminated.
    Short description of exception condition:
    At least one ID must be filled
    For detailed documentation of the exception condition, use  Transaction SE37 (Function Library). You can take the called
    function module from the display of active calls.
User and Transaction
    Client.............. 102
    User................ "WF-BATCH"
    Language key........ "E"
    Transaction......... " "
    Transactions ID..... "4C4E8E396A343C83E1000000C0A80106"
    Program............. "SAPLBP_CENTRAL_PERSON"
    Screen.............. "SAPMSSY0 1000"
    Screen line......... 6
Information on where terminated
    Termination occurred in the ABAP program "SAPLBP_CENTRAL_PERSON" - in
     "BP_CENTRALPERSON_GET".
    The main program was "RSWWDHEX_INTERNAL ".
    In the source code you have the termination point in line 183
    of the (Include) program "LBP_CENTRAL_PERSONU05".
    The program "SAPLBP_CENTRAL_PERSON" was started as a background job.
    Job Name....... "SWWDHEX"
    Job Initiator.. "WF-BATCH"
    Job Number..... 10372101
Thanks in advance.
Regards,
Dexter

Answer 1

Hi Dexter Marius,
Please see the Note: 1134889.
Summary
Symptom
When you use transaction BBP_POC to display or change a purchase order, a dump "NO_CENTRAL_PERSON" occurs in the program SAPLBP_CENTRAL_PERSON. The dump can occur only if the person who is the requester has left the company in the meantime.
Other terms
SAPLBP_CENTRAL_PERSON, dump, NO_CENTRAL_PERSON, BBP_POC
Solution
Implement the attached corrections.
Header Data
Release Status: Released for Customer
Released on: 26.09.2008  13:46:40
Master Language: German
Priority: Correction with high priority
Category: Program error
Primary Component: SRM-EBP-PD Procurement Document Methods
Affected Releases
Software
Component Release From
Release To
Release And
subsequent
SRM_SERVER 500 500 500  
SRM_SERVER 550 550 550  
SRM_SERVER 600 600 600  
Correction delivered in Support Package
Support
Packages Release Package
Name
SRM_SERVER 500 SAPKIBKS13
SRM_SERVER 550 SAPKIBKT12
SRM_SERVER 600 SAPKIBKU05
Corrections Instructions
Correction
Instruction Valid
from Valid
to Software
Component Last
Modifcation
600319 500 500 SRM_SERVER 23.01.2008  08:55:07
600320 550 550 SRM_SERVER 23.01.2008  08:55:23
657322 600 600 SRM_SERVER 26.09.2008  13:46:27
FORM CHECK_DELIMITED_PARTNER
Delta001Context Block 
  CALL FUNCTION 'BP_CENTRALPERSON_GET'
    EXPORTING
      iv_bu_partner_guid = lv_partner_no
    IMPORTING
      EV_USERNAME               = lv_username
Delete Block 
Insert Block 
    EXCEPTIONS
      NO_CENTRAL_PERSON         = 1
      NO_BUSINESS_PARTNER       = 2
      NO_ID                     = 4
      OTHERS                    = 5
  IF sy-subrc NE 0.
    lv_msgv1 = lv_partner_no.
    CALL FUNCTION 'BBP_PD_MSG_ADD'
      EXPORTING
        i_msgty       = c_msgty_e
        i_msgid       = 'BBP_PD'
        i_msgno       = 239
        i_msgv1       = lv_msgv1
      EXCEPTIONS
        log_not_found = 1
        OTHERS        = 2.
    IF sy-subrc <> 0.
      PERFORM abort.
    ENDIF.
    IF c_on = c_off. MESSAGE e239(bbp_pd) WITH lv_msgv1. ENDIF.
  ENDIF.
Regards,
Md Ziauddin.