-
Products and Technology
By Category
-
Groups
Activity Groups
Industry Groups
Influence and Feedback Groups
Interest Groups
Location Groups
Customer Only Groups
- Developers
- Partners
- Events
- Help Center
- Topic Pages
-
Explore SAP
Products
- Autonomous Enterprise
- Artificial intelligence
- Data and analytics
- Autonomous Suite
- Technology platform
- Transformation management
- Midsize business solutions
- Financial management
- Spend management
- Supply chain management
- Human capital management
- Customer experience
- Enterprise resource planning
- Business network
- Sustainability management
- SAP Store
- Try SAP
- View all industries
- Partners
- Services
Learning and Support
-
- Products and Technology
- Groups
- Developers
- Partners
- Events
- Help Center
- Topic Pages
-
Explore SAP
- Explore SAP
-
Products
- Products
- Autonomous Enterprise
- Artificial intelligence
- Data and analytics
- Autonomous Suite
- Technology platform
- Transformation management
- Midsize business solutions
- Financial management
- Spend management
- Supply chain management
- Human capital management
- Customer experience
- Enterprise resource planning
- Business network
- Sustainability management
- SAP Store
- Try SAP
- View all industries
- Partners
- Services
- Learning and Support
- About
- SAP Community
- Groups
- Interest Groups
- Application Development and Automation
- Discussions
- ABAP Dump CX_SY_DYN_CALL_PARAM_MISSING
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
ABAP Dump CX_SY_DYN_CALL_PARAM_MISSING
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2014 Aug 06 9:01 AM
- SAP Managed Tags
- ABAP Development
- ABAP Testing and Analysis
Hi Experts,
I am getting the below dump while clicking on the check button in tcode /cockpit/1. Below dump is happening. Any suggestion to come out of this?
Category ABAP Programming Error
Runtime Errors PERFORM_PARAMETER_MISSING
Except. CX_SY_DYN_CALL_PARAM_MISSING
ABAP Program /COCKPIT/SAPLPROCESS46C
Application Component Not Assigned
Date and Time 05.08.2014 12:01:21
| Error analysis |
| An exception occurred that is explained in detail below. |
| The exception, which is assigned to class 'CX_SY_DYN_CALL_PARAM_MISSING', was |
| not caught in |
| procedure "/COCKPIT/BAPI_INCINV_CREATE" "(FUNCTION)", nor was it propagated by |
| a RAISING clause. |
| Since the caller of the procedure could not have anticipated that the |
| exception would occur, the current program is terminated. |
| The reason for the exception is: |
| A PERFORM was used to call the routine "CO_FILL" of the program "SAPLMRM_BAPI". |
| The current call contains 6 actual parameter(s), |
| but the routine "CO_FILL" expects 10 parameters. |
| How to correct the error |
| Correct the PERFORM call. You can find out where the call |
| occurs in the section "Active calls / events". |
| If the error occures in a non-modified SAP program, you may be able to |
| find an interim solution in an SAP Note. |
| If you have access to SAP Notes, carry out a search with the following |
| keywords: |
| "PERFORM_PARAMETER_MISSING" "CX_SY_DYN_CALL_PARAM_MISSING" |
| "/COCKPIT/SAPLPROCESS46C" or "/COCKPIT/LPROCESS46CU04" |
| "/COCKPIT/BAPI_INCINV_CREATE" |
| Information on where terminated |
| Termination occurred in the ABAP program "/COCKPIT/SAPLPROCESS46C" - in |
| "/COCKPIT/BAPI_INCINV_CREATE". |
| The main program was "/COCKPIT/BAPI_MM_CREATE_INT ". |
| In the source code you have the termination point in line 180 |
| of the (Include) program "/COCKPIT/LPROCESS46CU04". |
| The program "/COCKPIT/SAPLPROCESS46C" was started as a background job. |
| Job Name....... "ZRS_DOC_CHECK" |
| Job Initiator.. "BASIS1" |
| Job Number..... 10000200 |
| The termination is caused because exception "CX_SY_DYN_CALL_PARAM_MISSING" |
| occurred in |
| procedure "/COCKPIT/BAPI_INCINV_CREATE" "(FUNCTION)", but it was neither |
| handled locally nor declared |
| in the RAISING clause of its signature. |
| The procedure is in program "/COCKPIT/SAPLPROCESS46C "; its source code begins |
| in line |
| 1 of the (Include program "/COCKPIT/LPROCESS46CU04 ". |
| 150 | |
| 151 | IF lb_afs_itemdata = con_true. |
| 152 | * SAP AFS compatibility |
| 153 | PERFORM (con_afs_frseg_fill) |
| 154 | IN PROGRAM (con_saplmrm_bapi) |
| 155 | TABLES it_bapi_item |
| 156 | it_bapi_account |
| 157 | it_bapi_afs_itemdata " SAP AFS |
| 158 | USING ls_rbkpv-waers |
| 159 | CHANGING lt_frseg[] |
| 160 | et_message[] |
| 161 | li_subrc. |
| 162 | ELSE. |
| 163 | PERFORM (con_afs_frseg_fill) |
| 164 | IN PROGRAM (con_saplmrm_bapi) |
| 165 | TABLES it_bapi_item |
| 166 | it_bapi_account |
| 167 | USING ls_rbkpv-waers |
| 168 | CHANGING lt_frseg[] |
| 169 | et_message[] |
| 170 | li_subrc. |
| 171 | ENDIF. |
| 172 | CHECK li_subrc LT 8. |
| 173 | |
| 174 | PERFORM co_fill(saplmrm_bapi) |
| 175 | TABLES it_bapi_gl_account |
| 176 | USING ls_rbkpv-waers |
| 177 | CHANGING lt_co[] |
| 178 | et_message[] |
| 179 | li_subrc. |
| >>>>> | CHECK li_subrc LT 8. |
| 181 |
BR.
Hi Experts,
I am getting the below dump while clicking on the check button in tcode /cockpit/1. Below dump is happening. Any suggestion to come out of this?
Category ABAP Programming Error
Runtime Errors PERFORM_PARAMETER_MISSING
Except. CX_SY_DYN_CALL_PARAM_MISSING
ABAP Program /COCKPIT/SAPLPROCESS46C
Application Component Not Assigned
Date and Time 05.08.2014 12:01:21
| Error analysis |
| An exception occurred that is explained in detail below. |
| The exception, which is assigned to class 'CX_SY_DYN_CALL_PARAM_MISSING', was |
| not caught in |
| procedure "/COCKPIT/BAPI_INCINV_CREATE" "(FUNCTION)", nor was it propagated by |
| a RAISING clause. |
| Since the caller of the procedure could not have anticipated that the |
| exception would occur, the current program is terminated. |
| The reason for the exception is: |
| A PERFORM was used to call the routine "CO_FILL" of the program "SAPLMRM_BAPI". |
| The current call contains 6 actual parameter(s), |
| but the routine "CO_FILL" expects 10 parameters. |
| How to correct the error |
| Correct the PERFORM call. You can find out where the call |
| occurs in the section "Active calls / events". |
| If the error occures in a non-modified SAP program, you may be able to |
| find an interim solution in an SAP Note. |
| If you have access to SAP Notes, carry out a search with the following |
| keywords: |
| "PERFORM_PARAMETER_MISSING" "CX_SY_DYN_CALL_PARAM_MISSING" |
| "/COCKPIT/SAPLPROCESS46C" or "/COCKPIT/LPROCESS46CU04" |
| "/COCKPIT/BAPI_INCINV_CREATE" |
| Information on where terminated |
| Termination occurred in the ABAP program "/COCKPIT/SAPLPROCESS46C" - in |
| "/COCKPIT/BAPI_INCINV_CREATE". |
| The main program was "/COCKPIT/BAPI_MM_CREATE_INT ". |
| In the source code you have the termination point in line 180 |
| of the (Include) program "/COCKPIT/LPROCESS46CU04". |
| The program "/COCKPIT/SAPLPROCESS46C" was started as a background job. |
| Job Name....... "ZRS_DOC_CHECK" |
| Job Initiator.. "BASIS1" |
| Job Number..... 10000200 |
| The termination is caused because exception "CX_SY_DYN_CALL_PARAM_MISSING" |
| occurred in |
| procedure "/COCKPIT/BAPI_INCINV_CREATE" "(FUNCTION)", but it was neither |
| handled locally nor declared |
| in the RAISING clause of its signature. |
| The procedure is in program "/COCKPIT/SAPLPROCESS46C "; its source code begins |
| in line |
| 1 of the (Include program "/COCKPIT/LPROCESS46CU04 ". |
| 150 | |
| 151 | IF lb_afs_itemdata = con_true. |
| 152 | * SAP AFS compatibility |
| 153 | PERFORM (con_afs_frseg_fill) |
| 154 | IN PROGRAM (con_saplmrm_bapi) |
| 155 | TABLES it_bapi_item |
| 156 | it_bapi_account |
| 157 | it_bapi_afs_itemdata " SAP AFS |
| 158 | USING ls_rbkpv-waers |
| 159 | CHANGING lt_frseg[] |
| 160 | et_message[] |
| 161 | li_subrc. |
| 162 | ELSE. |
| 163 | PERFORM (con_afs_frseg_fill) |
| 164 | IN PROGRAM (con_saplmrm_bapi) |
| 165 | TABLES it_bapi_item |
| 166 | it_bapi_account |
| 167 | USING ls_rbkpv-waers |
| 168 | CHANGING lt_frseg[] |
| 169 | et_message[] |
| 170 | li_subrc. |
| 171 | ENDIF. |
| 172 | CHECK li_subrc LT 8. |
| 173 | |
| 174 | PERFORM co_fill(saplmrm_bapi) |
| 175 | TABLES it_bapi_gl_account |
| 176 | USING ls_rbkpv-waers |
| 177 | CHANGING lt_co[] |
| 178 | et_message[] |
| 179 | li_subrc. |
| >>>>> | CHECK li_subrc LT 8. |
| 181 |
BR.
Bluesky
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2014 Aug 06 9:10 AM
- SAP Managed Tags
- ABAP Development
- ABAP Testing and Analysis
Hi
I don't know fm (BAPI /COCKPIT/BAPI_INCINV_CREATE), but something is missing (or an exception or import/export parameter)
Max
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2014 Aug 06 9:56 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2014 Aug 06 9:59 AM
- SAP Managed Tags
- ABAP Development
- ABAP Testing and Analysis
You should post how that BAPI is called, I suppose that BAPI is a custon BAPI as copy of a std one (probably BAPI_INCOMINGINVOICE_CREATE)
Max
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2014 Aug 06 10:09 AM
- SAP Managed Tags
- ABAP Development
- ABAP Testing and Analysis
Try to check PERFORM co_fill(saplmrm_bapi)
How that form is defined?
| A PERFORM was used to call the routine "CO_FILL" of the program "SAPLMRM_BAPI". |
| The current call contains 6 actual parameter(s), |
| but the routine "CO_FILL" expects 10 parameters. |
I suppose there's an error
Max
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2014 Aug 06 10:44 AM
- SAP Managed Tags
- ABAP Development
- ABAP Testing and Analysis
Hi,
What are your NetWeaver and SAP_APPL Releases; have there been upgrades on this system recently? On NW 702 and SAP_APPL 605 SP 08, the subroutine CO_FILL of SAPLMRM_BAPI still contains only 6 parameters...
The /cockpit/ namespace looks like belonging to either SAP standard application or to some SAP partner development. There maybe mismatch between the release levels of the components. If you find the package(s) /cockpit/ stuff belongs to, the software component field should give an idea, where to start looking.
I'd be complaining loudly, if it turned out some SAP partner developed solution having the kind of dependencies to SAP internal interfaces like the Form Routine calls in that short dump... The least that the team programming stuff like that should have done IMO, is to catch all the dynamic call exceptions possible and output a humane message saying: something has changed in SAP Standard - you might need to get a new version of /cockpit here and there...
cheers
Janis
Message was edited by: Jānis B
