Creation of CAPI Definition fails

Within Headstart Utilities the creation of all CAPI Definitions fails with Error Messages "Activity aborted with ORACLE internal errors" and "ORA-06508: PL/SQL: could not find program unit being called".
It seems that this caused due package hsu_capc:
BLAPI.OPEN_ACTIVITY
Start HSU_CAPI.run
Number of Tables to create CAPI for 1
Initial checks for table DBE_ACCESSIBILITIES with id 126949878011559489794221642994244829
HSU_CAPT.initial_checks for table DBE_ACCESSIBILITIES
HSU_CAPF.initial_checks for table DBE_ACCESSIBILITIES
HSU_CAPC.initial_checks Custom Services for table DBE_ACCESSIBILITIES
Activity aborted with ORACLE internal errors.
-6508 ORA-06508: PL/SQL: could not find program unit being called
All Headstart packages are valid. Has anyone an idea or suggestion for solving this problem?

Hello Rinie,
It looks like you're missing a HSU-program-unit.
You might want to check the installation-folder for the presence of HSU_CAPB, needed to create the package-body.
Succes!

Similar Messages

Custom Capi service definition fails to include in Capi

I am working on a migrated Oracle designer repository and have quite a lot of custom Capi service definitions which would normally appear in the Capi that they apply to, once I run "Create Capi Definition".
However they are steadfastly refusing to appear. If I go and create a new custom Capi service definition, the new one will appear, but not the old ones.
This could be a simple oversight that I am experiencing - can anyone suggest a resolution to this problem.
I am using hss_capi Rev: 6.5.4.0.2
Regards
Phil Gray

Please note this has been resolved.
For some reason the table definition has been dropped off the CAPI Custom Service program data properties.
This is found by opening the PL/SQL definition for the custom capi service in the Repository Object Navigator.
As for the reason the definition has gone.....?

Creation of upgrade packages fails

Dear all
We did an upgrade from 4.0 to 2007, but now found out among other things that the MUP definition in the upgrade console was not updated. As such if we now want to create a new upgrade package with the predefined units (BOL, BDOc and UI) the creation of these units fails as some files are missing.
Does anybody know: Were the units redefined when upgrading to 5.0? And if so, how can I get my hands on one of these as I do not want to try and build the UI and BOL packages myself from scratch.
Thanks in advance,
Kai

Thanks Shankar,
The not does not apply (as 2007 SP2 which we are on is 5.0SP11 and the note is SP09 only), but via connecting notes I found the note 1156416 (did not help) and finally 1171933 which provided the correct solution.
Regards, Kai
Edited by: Kai Blanke on Jan 16, 2009 10:35 AM
Set question to solved

-6502 ORA-06502: PL/SQL: numeric or value error when using 'Create CAPI Definition'

I get an error when I try to create a CAPI definition with Headstart untilities (6i). I use HSU_CAPI revision 6.5.2.0
The detailed information says the following:
Message
BLAPI.OPEN_ACTIVITY
Start HSU_CAPI.run
Number of Tables to create CAPI for 1
Initial checks for table KCS_TENDERS with id 692754610572409851363604771392473242
HSU_CAPT.initial_checks for table KCS_TENDERS
HSU_CAPF.initial_checks for table KCS_TENDERS
HSU_CAPC.initial_checks Custom Services for table KCS_TENDERS
HSU_CAPB.initial_checks BRDD for table KCS_TENDERS
bltext.get_lines_from_repository, p_text_type=CDINOT
bltext.get_line_containing
bltext.get_line_containing
bltext.get_lines_from_repository, p_text_type=CDIPLS
bltext.get_line_containing
bltext.get_line_containing
bltext.get_line_containing
bltext.get_line_containing
bltext.get_line_containing
bltext.get_line_containing
KCS_TENDERS Business Rule Design Definition BR_TNR001_CEV does not have any Trigger Columns. Rule will fire when any column is updated.
bltext.get_lines_from_repository, p_text_type=CDINOT
bltext.get_line_containing
bltext.get_line_containing
bltext.get_lines_from_repository, p_text_type=CDIPLS
bltext.get_line_containing
bltext.get_line_containing
bltext.get_line_containing
bltext.get_line_containing
bltext.get_line_containing
bltext.get_line_containing
Creating CAPI for table KCS_TENDERS with id 692754610572409851363604771392473242
Recreating KCS_TENDERS Table API/Trigger Logic - Event: Pre-Before-Insert-stmt, Open transaction.
Write Text for element type APPLOG with id 753236628580304413262318236391196826 - Text type: ALCODE number of text lines = 6 - REPLACE
Deleted old text
Write Text for element type APPLOG with id 753236628580304413262318236391196826 - Text type: ALCMNT number of text lines = 1 - REPLACE
Deleted old text
Recreating KCS_TENDERS Table API/Trigger Logic - Event: Pre-Before-Update-stmt, Open transaction.
Write Text for element type APPLOG with id 753236628580332747461215454262479002 - Text type: ALCODE number of text lines = 6 - REPLACE
Deleted old text
Write Text for element type APPLOG with id 753236628580332747461215454262479002 - Text type: ALCMNT number of text lines = 1 - REPLACE
Deleted old text
Recreating KCS_TENDERS Table API/Trigger Logic - Event: Pre-Before-Delete-stmt, Open transaction.
Write Text for element type APPLOG with id 753236628580361081660112672133761178 - Text type: ALCODE number of text lines = 6 - REPLACE
Deleted old text
Write Text for element type APPLOG with id 753236628580361081660112672133761178 - Text type: ALCMNT number of text lines = 1 - REPLACE
Deleted old text
Recreating KCS_TENDERS Table API/Trigger Logic - Event: Post-After-Insert-stmt, Close transaction.
Write Text for element type APPLOG with id 753236628580389415859009890005043354 - Text type: ALCODE number of text lines = 6 - REPLACE
Deleted old text
Write Text for element type APPLOG with id 753236628580389415859009890005043354 - Text type: ALCMNT number of text lines = 1 - REPLACE
Deleted old text
Recreating KCS_TENDERS Table API/Trigger Logic - Event: Post-After-Update-stmt, Close transaction.
Write Text for element type APPLOG with id 753236628580417750057907107876325530 - Text type: ALCODE number of text lines = 6 - REPLACE
Deleted old text
Write Text for element type APPLOG with id 753236628580417750057907107876325530 - Text type: ALCMNT number of text lines = 1 - REPLACE
Deleted old text
Recreating KCS_TENDERS Table API/Trigger Logic - Event: Post-After-Delete-stmt, Close transaction.
Write Text for element type APPLOG with id 753236628580446084256804325747607706 - Text type: ALCODE number of text lines = 6 - REPLACE
Deleted old text
Write Text for element type APPLOG with id 753236628580446084256804325747607706 - Text type: ALCMNT number of text lines = 1 - REPLACE
Deleted old text
Recreating KCS_TENDERS Table API/Trigger Logic - Event: Pre-Before-Delete-row, Save old data.
Write Text for element type APPLOG with id 753236628580474418455701543618889882 - Text type: ALCODE number of text lines = 404 - REPLACE
Deleted old text
Write Text for element type APPLOG with id 753236628580474418455701543618889882 - Text type: ALCMNT number of text lines = 1 - REPLACE
Deleted old text
Recreating KCS_TENDERS Table API/Trigger Logic - Event: Pre-Insert, Call CAPI.
Write Text for element type APPLOG with id 753236628580568865785358936523163802 - Text type: ALCODE number of text lines = 4 - REPLACE
Deleted old text
Write Text for element type APPLOG with id 753236628580568865785358936523163802 - Text type: ALCMNT number of text lines = 1 - REPLACE
Deleted old text
Recreating KCS_TENDERS Table API/Trigger Logic - Event: Pre-Update, Call CAPI.
Write Text for element type APPLOG with id 753236628580597199984256154394445978 - Text type: ALCODE number of text lines = 4 - REPLACE
Deleted old text
Write Text for element type APPLOG with id 753236628580597199984256154394445978 - Text type: ALCMNT number of text lines = 1 - REPLACE
Deleted old text
Recreating KCS_TENDERS Table API/Trigger Logic - Event: Pre-Delete, Call CAPI.
Write Text for element type APPLOG with id 753236628580625534183153372265728154 - Text type: ALCODE number of text lines = 17 - REPLACE
Deleted old text
Write Text for element type APPLOG with id 753236628580625534183153372265728154 - Text type: ALCMNT number of text lines = 1 - REPLACE
Deleted old text
Recreating KCS_TENDERS Table API/Trigger Logic - Event: Post-Insert, Call CAPI.
Write Text for element type APPLOG with id 753236628580653868382050590137010330 - Text type: ALCODE number of text lines = 7 - REPLACE
Deleted old text
Write Text for element type APPLOG with id 753236628580653868382050590137010330 - Text type: ALCMNT number of text lines = 1 - REPLACE
Deleted old text
Recreating KCS_TENDERS Table API/Trigger Logic - Event: Post-Update, Call CAPI.
Write Text for element type APPLOG with id 753236628580682202580947808008292506 - Text type: ALCODE number of text lines = 144 - REPLACE
Deleted old text
Write Text for element type APPLOG with id 753236628580682202580947808008292506 - Text type: ALCMNT number of text lines = 1 - REPLACE
Deleted old text
Recreating KCS_TENDERS Table API/Trigger Logic - Event: Post-Delete, Call CAPI.
Write Text for element type APPLOG with id 753236628580767205177639461622139034 - Text type: ALCODE number of text lines = 282 - REPLACE
Deleted old text
Write Text for element type APPLOG with id 753236628580767205177639461622139034 - Text type: ALCMNT number of text lines = 1 - REPLACE
Deleted old text
HSU_CAPF.create_or_find_capi_pack
hsu_capi.find_plm (kcs_tnr_capi, 692754610572409851363604771392473242, CAPI).
capi package found in the context folder
BLPLM.UPD
FREE_FORMAT_TEXT_FLAG......... = Y
IMPLEMENTATION_NAME........... = kcs_tnr_capi
PLSQL_MODULE_TYPE............. = PACKAGE
SCOPE......................... = PUBLIC
COMPLETION_STATUS............. = COMPLETED
NAME.......................... = kcs_tnr_capi
PURPOSE....................... = Custom API package for implementing Business Rules and supporting TAPI
Recreated Package KCS/ KCS_TNR_CAPI, preserving only the Revision History.
HSU_CAPF.add_tags_er_av
bltext.get_lines_from_repository, p_text_type=CDINOT
bltext.get_line_containing
bltext.get_line_containing
bltext.get_lines_from_repository, p_text_type=CDINOT
bltext.get_line_containing
bltext.get_line_containing
bltext.get_lines_from_repository, p_text_type=CDINOT
bltext.get_line_containing
bltext.get_line_containing
bltext.get_lines_from_repository, p_text_type=CDINOT
bltext.get_line_containing
bltext.get_line_containing
HSU_CAPF.create_specification
HSU_CAPF.create_c_tabalias
HSU_CAPF.create_c_tabalias_all
HSU_CAPF.create_aggregate_value
HSU_CAPF.create_aggregate_value
HSU_CAPF.create_aggregate_value
Activity aborted with ORACLE internal errors.
-6502 ORA-06502: PL/SQL: numeric or value error: character string buffer too small
What can I do about it???
Thanks in advance.
Menno Hoogsteen

Working on the same project as Menno, I had the time to look into the problem.
The problem is caused by the creation of the capi-function agregate_char_value in the packages hsu_capf. While creating this function the following code is executed:
add(' -- allowable values:');
add(' -- '||l_col_name_list);
This last statement causes the problem because this table is very big. L_col_name_list contains 2391 characters wich is 393 characters to long. So i changed this code into:
add(' -- allowable values:');
add(' -- '||substr(l_col_name_list,1,1990));
add(' -- '||substr(l_col_name_list,1990));
and everything works fine. Perhaps something for a patch?
Kind regards,
Ruben Spekle

Creation of project definition and wbs element

I want creation of project definition and wbs element upto 4 level using bapis.
i am using transaction cj27,cj01,cj02
which function module to use for this??

Hi,
to create project definition with customer fields the BAPI you should use is : BAPI_BUS2001_CREATE
to create WBS elements with different levels and specific fields the BAPI you should use is BAPI_BUS2054_CREATE_MULTI
these bapi must be used in the sequence of call :
BAPI_PS_INITIALIZATION
BAPI_BUS2001_CREATE / BAPI_BUS2054_CREATE_MULTI
BAPI_PS_PRECOMMIT
BAPI_TRANSACTION_COMMIT
before using the bapi, you must apply OSS note :
637345 - Syntax error with enhanced PS tables
i sent you the oss note to your mail
please reward points if helpfull.

What technology that can be used for the creation of Need Definition?

Being on SAP SRM 4.0, we currently have a requirement for creation of Need Definition( Basically a build up for the contract ). Need being collected from the Backend systems need to be validated and approved by Buyers & Lead Buyers in the SRM system.
Technically, this task is broken down to below tasks.
1) Creation of need definition screen - Basically a template where a need can be created with Items, Sub Items and other related information
2) Selection Screen for Buyers and Lead Buyers - This enables the the Buyers to select the Need Definition assigned to them based on the status.
3) Report - List of all the Need Definition( Item and Sub Item)satisfying the selection of step 2. with the possibility to navigate to the Need Definition screen ( Step 1) upon selection.
Now the question is,
what technology is recommended for the above Tasks? We thought it would be BSP but do you guys have any suggestions...
Do we have any issues in displaying the report in BSP? please let me know
Remember we are version 4.0 of SRM.
Thanks in Advance..
Mohan.

You can use conditional styles to address specific browser issues (this is more than likely the markup you noticed).
Here's a good guide:
http://www.quirksmode.org/css/condcom.html

Creation of login object failed

Hi all,
I've got a problem with the mobile client development.
We are using the mobile client for many years and we even develop a lot with it, but now i have a problem never seen.
After extending a bDoc and start testing the application, after the generation and login, system states "Creation of login object failed".
So i did a full generation. Result the same.
I debugged the ValidateLogin class and found out, that in the following statement is failing
       BOLOGIN = BusinessRootObject.BusinessFactory.LoadBusinessObject("LOGIN", determineUser)
BOLOGIN is Nothing at the end. I tried out to create the Object via        BOLOGIN = BusinessRootObject.BusinessFactory.CreateBusinessObject("LOGIN")
same result. Next i tried to create the BOACTIVITY and it failed as well. One day before everything was fine, even with changing business documents.
The error in the VB.ERR object says:
-     err     {Microsoft.VisualBasic.ErrObject}     Microsoft.VisualBasic.ErrObject
     Description     "In der Methode BusinessFactoryCore.LoadBusinessObject ist eine System-Exception aufgetreten"     String
     Erl     0     Integer
     HelpContext     0     Integer
     HelpFile     ""     String
     LastDllError     3     Integer
     Number     5     Integer
     Source     "MTBLLFW"     String
Can anybody please give a hint.
We are using CRM 5.0 SP7 and MSA SP7 on MS 2003 Server with local repository. DB is SQL2000.
Yesterday i was releasing a changelist and now its no longer working at all, what a mess.
Thanks to all,
Andreas Rose

Hi Andreas,
The problem may be incorrect or corrupt ARSREP.DAT file.
The reason may be that the BDOCs are not synched from MAS. Once you sync this through MAS you will find the *.bdoc files at the location
mentioned under the registry key HKLM\SOFTWARE\SAP\MSA\MW\TL\BDocPath
Usually this would be default as C:\Program Files\SAP\Mobile\tpsfiles.
After this when you generate the BusinessLibrary the Arsrep.dat file
will have the *.bdocs incorporated in the Arsrep.dat file.
Hope this helps.
Regards, Gervase
ps. For synching the BDocs refer to SAP Note 942942

Error while Debugging MSA 'Creation of Login Object Failed'

Dear Friends,
I am working on CRM Mobile Sales 5.0 SP 5.
I have setup my Mobile Client and Mobile Application Studion On the same machine.
I have perform the initial generation of the application from Mobile Repository server to my machine.
it gave me 6 errors and 12 warnings and took about 4 hrs for generation.
Now when i tried to debug the generated application,
i get my login screen and once I enter username and password.
Error popups up stating "Creation of login object failed".
and then another error
"Starting MPPFailed" (MPP is my project name).
Please suggest me how should i go about to debug the application solving the above errors.
Awaiting Reply,
Best Regards,
Pratik Patel

Am not sure if you were able to resolve the issue but below are some points:
a. I think the dlls sfabol and msa are not any more registerable, since they are more of VB.NET components and here assembly is registered and not the dll.
b. For logging into the application just ensure that you have user id in table SMOUSER and the employee for that user in SMOMITABT table.
c. If this is fine, then ensure that you have the latest BDOC metadata information on your laptop. I think in 5.0 also you need to use Clientconsole to download this information.
d. If this is all okay, then try running SQL profiler and check if the query to the ides db is being executed by the framework. If the query is fired then it means application seems to behave properly but the query is not retrieving relevant details.
For further details feel free to contact me..
thanks,
Piyush

"Creation of login object failed" after MAS generation

Hi everybody,
I am working on CRM Mobile Sales 5.0 SP6. I have performed the initial generation with the .NET Application Studio. It gave me 6 errors and some warnings. Now when I tried to logon my mobile client I 've got following error:
"Creation of login object failed".
Visual Studio is installed on partition "C:\Program Files\" and Mobile Sales on "D:\SAP\"
Has someone any ideas? Thanks in advance,
Mirko

Hi Mirko!
In your app you're calling unknown data structures. While generating the "compiler" read the names and want to create the relevant structures but the necessary data to do this are missing. You have to start fist the client console doing a complete meta data generation. If this runs without error your generation inside the studio will succeed, too.
BTW: In your first posting you've written "D:SAP..." and in your last the error-message was "D:ProgrammeSAP..."...
Perhaps different settings?
Do you have made already a successful generation with the actual installation?
Good luck,
Ingo
Message was edited by:
Ingo Schmökel

The creation of export datasource failed.

Hi everyone! This is Chong Tao from Central Michigan University and I got one problem recently when I was doing my set-up of the BW course. I actually wanna copy the infocube but when I click the "Generate export datasource", it automatically comes up one error message "The creation of export Datasource failed". What should I do to overcome this problem? Thanks for paying attention to this problem and I need your valuable advice as soon as possible since it is for the student in this SAP BW course.

Hi,
I guess your objective is to copy an existing infocube. Right ?
In that case, Right Click Infocube and use 'copy'. This will create another Infocube with the same structure, but with no data. You can then fill this copy Infocube by cerating transformation between the two infocubes and scheduling through DTP.
'Generate export datasource' can normally be done when there are two separate BW systems and you want an Infocube to be a source of data to another Infocube in a different BW system( though it can be used in the same BW system as well).
Best Regards

Create CAPI definition problem with Headstart 6i / Designer 6i rel. 4.3

During migration from hsd50/des60 to hsd65/des6i rel 4.3 of an application using CDM ruleframe: according to the migration guide, one step is "Upgrading Existing CDM RuleFrame objects", which includes running the Create CAPI definition (Headstart utility). After that step we assume de created CAPI's should be generated together with the Table API. But executing the CAPI-scripts results in errormessages. After comparing the 60 and 6i versions, we found a bug, probably caused by the Headstart utility: In the package body, after the header of the first function of the Business Rule Check Functions, suddenly the declaration section of the package is again inserted, and after that the first function is again defined followed by the rest, causing also a missing end statement at the end of the package.
Is this known, and if so, is there a fix available?
Regards, Paul.

Paul,
We have found the cause for your other problem (the repeating of the declaration section).
With 6.5 a new package property Private Declaration was introduced in Designer.
This property should officially be used instead of PL/SQL block to specify package body declaration
(assuming you define all package procedures and functions in separate PL/SQL Definitions).
However, at first the migration from an earlier version of Designer did not pose any problems
because of Designer bug 1470283. That's why you won't find anything about this in the Headstart Migration Guide.
Now that Designer bug is fixed, migrating a CAPI causes part of the PL/SQL Block to be moved to the Private Declaration.
If you then generate the CAPI package to the database, it works fine, but when you run the CAPI utility again,
it inserts the package declarations again in the PL/SQL Block (leaving the Private Declaration in tact).
That's when you get duplicate package declarations. We logged this as Headstart bug 2527128.
You already found a workaround: deleting the CAPI and generating it again. Another workaround is
moving the Private Declaration to the top of the PL/SQL Block (this allows you to keep your existing
Revision History).
Hope this helps,
Sandra

EDQP: After creation of Item definition, not able to find the the same item in Standardize items tab.

Hello Experts,
This is the first time am creating the item definition in the data lens, after creation of item definition, thought of standardizing it through Standardization Items tab. Not able to find the created item definition in the Item Definition Field LOV.
Do we need to do any set up to get it available in the Standardization Items tab. For information, I found two things as follows
1.this item has not assigned to any of sample data records.
2.Did not find created item definition name in the Item definition field..( It has showing only text as 'Not Item Definition')
Can any plz help me in creating Item definition completely. After gone through the Knowledge studio ref guide developed to some extent.
Thanks,
SSagar.

Can you put some screenshots of what you did and what you are seeing?

"New lifecycle definition" fails with "Unexpected error"

This problem has been previously posted without resolution.
Select "Lifecycle Definitions -> New lifecycle definition".
Error:
"Unexpected error, unable to find item name at application or page level.
A severe error has occurred. Possible causes may include moving directly to a page using the browser history or Back key, multiple users attempting to change the same data or an application defect. Please visit the Support page under the Help Tab to report the error.
Press here to return to the parent page"
A resolution to this would be apprciated.
Please note this problem is based on APEX 4. About to retest on APEX 3.2 to see if it is happening there.
Edited by: user774105 on 7/03/2011 17:26
Have back ported to 3.2 and the problem no longer occurs. Not sure what has changed between versions, but there are a number of links in the Assitant that fail with the above error in APEX 4.
Edited by: user774105 on 7/03/2011 19:45

Hi
I have also encounter the same error . Currently i have apex version 4.
User: SYSTEM
Unexpected error, unable to find item name at application or page level.
A severe error has occurred. Possible causes may include moving directly to a page using the browser history or Back key, multiple users attempting to change the same data or an application defect. Please visit the Support page under the Help Tab to report the error.
Press here to return to the parent page
Any solution for this with apex version 4
Thanks and Regards
Ganesan Sivaraman

The Creation of Export DataSource Failed Error while transporting ODS Cube

Hi All,
I am facing this issue from last 1 week.. i had developed an ODS cube in APO-DP BW which will fetch data from SAP R/3 and its working fine in APO Dev Server. But when i transport this cube into APO PAC(Prodn Server) the below error i am getting..
   Start of the after-import method RS_ODSO_AFTER_IMPORT for object type(s) ODSO (Activation Mode)
   The creation of the export DataSource failed
   Password logon no longer possible - too many failed attempts
   Password logon no longer possible - too many failed attempts
   Error when creating the export DataSource and dependent Objects
   Error when activating DataStore Object ZANAUTSL
I also updated the transport conversion tables but still problem not resolved.
Immediate help is hightly appreciated.
Thanx
AJ

Hi AJ,
Looking at your error, it seems that the RFC user's password is locked and hence connectivity from R/3 towards APO BW is broken.
You know the name of your export datasource (from R/3 to APO BW). Find out the name of your R/3 source system e.g. PACCLT000, by scrolling to the right against teh export data source.
Take help of your Basis or EAI team to identify the RFC destination corresponding to the connectivity from the R/3 source system (PACCLT000) to your APO BW system. (If needed ask for help from your BW team, I am not very sure how connectivity would be set up from R/3 to APO BW, I guess this would be independent from CIF connectivity)
For this RFC connection from R/3 to APO BW, see which RFC user is maintained in SM59 in APO and ask your security team to reset (or unlock) the password of this RFC user in R/3, and then if required update the user password details in SM59 in APO also.
After this, your issue should get resolved.
Thanks - Pawan

PO creation with call tranaction fails in a BDC program

Hi All,
There is a BDC with out client which creates Purchase order with the delivery numbers.
We are using the call transaction as shown below:
CALL TRANSACTION 'ME21'USING bdcdata UPDATE synch MODE display.
Where display = 'A"
Before that the BDC_DATA is filled as follows:
PERFORM dynpro USING:
   space        space space   'BDC_OKCODE'   'KOPF',
'SAPMM06E'    '101' 'X'     space          space ,
   space        space space   'EKKO-IHREZ'   int_lips-vbeln,
   space        space space   'EKKO-UNSEZ'   int_lips-vgbel,
   space        space space   'BDC_OKCODE'   '/11',
* Have to code past message screen and save, despite absence of output.
'SAPLSPO1'    '300' 'X'     space          space ,
   space        space space   'BDC_CURSOR'   'SPOP-OPTION1',
   space        space space   'BDC_OKCODE'   'YES'.
Now when we try to execute the report the report shows as a error message as follows:
System messages received during processing.
          S00                  378 Start screen does not exist in batch input data
          S00                  378 Above reason code caused PO Creation to fail.
Please help me understand why this happens.
Thanks & Regards,
Selvakumar M.

HI,
You can use the BAPI --> BAPI_PO_CREATE1 for PO creation.
Or there might be screen missing in the BDC can you show the BDC data fill program
Regards,
Madhukar Shetty

Creation of CAPI Definition fails

Similar Messages

Maybe you are looking for