Dear all,
I try to do movement type 107 for an inbound delivery with the BAPI_GOODSMVT_CREATE, but i have the following message :
"Goods movement not possible with mvmt type 107"
I don't understand what happen, because i can do this movement with MIGO transaction.
Thanks for your help
Eric
Hi Gurus,
Please guide me on how to populate SSM (Specified Shipping Method) field of segment E1S2K11 for S1BOOKED message type.
The scenario is to create a PO to vendor and transmit the PO via idoc and SSM (Specified Shipping Method) is a required field.
Thanks in advance.
Regards,
JJ
HI.. i am new to abap.. i want to update t code pa30 using bdc.. can you please tell me how can i do this...?????
Hi Experts
I use the BAPI " BAPI_ACC_PRIMARY_COSTS_POST" to post
primary costs.
I call the BAPI in a loop.
For evry record if the Message Type is "S' success i call the BAPI " BAPI_TRANSACTION_COMMIT"
For evry Message other than "S"
I call the BAP " BAPI_TRANSACTION_ROLLBACK". Here a get a short dump.
Cann any body explain please why.
Thanks a lot for any help.
King
Dear Experts,
I am MM-functional consultant, while suporting one process I came across one issue in which an Outbound IDOC is created via PO output and this in return creates SO.
I understand that there is one outbound IDOC and it created another Inbound IDOC corresponding to earlier IDOC. Both IDOC can be seen as related IDOC's in BD87 if we check the Outbound IDOC.
In my case Outbound IDOC is procesed and is green but the corresponding Inbound IDOC is not generated. I can manually trigger the Inbound IDOC using T-Code WE19 and the SO is generated. But with this process I cannot see both IDOC as related one's in BD87 while checking the Outbound IDOC.
This process is working well in other environments/system.
Plese advise where should I look for cause.
Thanks
Manish.
We are trying to implement RTI (Sending EAS, FPS, EPS etc... to HMRC) for UK Payroll. SAP has provided solution using XI/PI. Can we send the same information using Web Services alone?
Hi All,
Currently facing an issue regarding serialization type for Bommat which is an Standard IDoc.
Is their any standard process for serialization of Bommat IDoc from SAP?
If Yes then what type of ALE serialization can be done to Bommat?
Thanks,
sachin
Hi Experts,
I am running one BDC in which i am deleting a record if its value are not fully maintained and updating new values using QP02.
But i need a validation on one field that if there is no data in that specific filed then the popup for deletion needs to be cancellled.
Unfortunately i am not getting any code which can validate field during BDC.
Please help.
Hi Everyone,
I have started learning basis.
My Question is, there are four types of RFC communications.
1.Synchronous 2.Asynchronous 3.Transactional 4.Queued.
Where we will be mentioning/defining the RFC communication type in SAP?
Dear All,
I have to modify the code for a requirement, if the length of PO's item text exceeds 68 characters, the segment E1EDPT2 will not get created for both ORDERS and ORDCHG message type of a outbound idoc.
For this need, which user exit i am suppose to use. I have tried to debug both the user exit
EXIT_SAPLEINM_011 and EXIT_SAPLEINM_002, but its not stopping in the breakpoint.
Kindly suggest something.
Thanks.
Hi All,
I need to reprice a sales order while triggering an output type from the same. There are some exits like MV45AFZB -> FORM userexit_new_pricing_vbkd, which handle repricing but those are not triggered unless any change is made in VBAP or VBKD structures. I can have a scenario where no changes to the order will be made, yet on triggering output type, it should reprice the Order.
Please let me know if any such exits or Badi exists that is hit while triggering output types. I checked the output type routine that we have, but there is no way I can set any variable that will lead to repricing.
Hi All,
I am using the FM ITS BROWSER REDIRECT to call a new URL from the existing URL.
But it is not working. it is giving me a blank screen.
I have a ITS URL in which when I press a button I need to call another URL by closing the existing one.
I have also used CALL BROWSER
it opens the new URL but it doesn't close the existing URL.
can any one help in this
Hi Gurus,
Please guide me on how to populate SSM (Specified Shipping Method) field of segment E1S2K11 for S1BOOKED message type.
The scenario is to create a PO to vendor and transmit the PO via idoc and SSM (Specified Shipping Method) is a required field.
Thanks in advance.
Regards,
JJ
Hi Team,
As we are on the verge of SAP system go live.
We are building DR system in Windows 2008 R2 Microsoft cluster service with our Production system Export.
We have taken the SAP Export from production as High Availabilty mode and we have installed the oracle binaries same as production in our DR site (With out Oracle patch apply).
While applying the Oracle patch we are facing error.
We have completed our ACSC installtion and during the importing ABAP Phase, we are facing the error in IMPORT ABAP Phase.
Looking for solution from your End ASAP because now we are in go live critical phase.
Regards
Anirban
Error Below
================
WARNING 2014-02-24 21:22:38.902
Execution of the command "C:\sapjvm_4\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2_34"
Java(TM) 2 Runtime Environment, Standard Edition (build 4.1.019)
SAP Java Server VM (build 4.1.019 1.6-b11, Feb 15 2012 09:14:36 - 41_REL - optU - windows amd64 - 6 - bas2:166760 (mixed mode))
Import Monitor jobs: running 1, waiting 61, completed 0, failed 0, total 62.
Import Monitor jobs: running 2, waiting 60, completed 0, failed 0, total 62.
Import Monitor jobs: running 3, waiting 59, completed 0, failed 0, total 62.
Import Monitor jobs: running 4, waiting 58, completed 0, failed 0, total 62.
Import Monitor jobs: running 5, waiting 57, completed 0, failed 0, total 62.
Import Monitor jobs: running 6, waiting 56, completed 0, failed 0, total 62.
Import Monitor jobs: running 7, waiting 55, completed 0, failed 0, total 62.
Import Monitor jobs: running 8, waiting 54, completed 0, failed 0, total 62.
Import Monitor jobs: running 9, waiting 53, completed 0, failed 0, total 62.
Import Monitor jobs: running 10, waiting 52, completed 0, failed 0, total 62.
Import Monitor jobs: running 11, waiting 51, completed 0, failed 0, total 62.
Import Monitor jobs: running 12, waiting 50, completed 0, failed 0, total 62.
Import Monitor jobs: running 13, waiting 49, completed 0, failed 0, total 62.
Import Monitor jobs: running 14, waiting 48, completed 0, failed 0, total 62.
Import Monitor jobs: running 15, waiting 47, completed 0, failed 0, total 62.
Import Monitor jobs: running 16, waiting 46, completed 0, failed 0, total 62.
Import Monitor jobs: running 17, waiting 45, completed 0, failed 0, total 62.
Import Monitor jobs: running 18, waiting 44, completed 0, failed 0, total 62.
Import Monitor jobs: running 17, waiting 43, completed 0, failed 2, total 62.
Import Monitor jobs: running 18, waiting 42, completed 0, failed 2, total 62.
Import Monitor jobs: running 19, waiting 41, completed 0, failed 2, total 62.
Import Monitor jobs: running 20, waiting 40, completed 0, failed 2, total 62.
Import Monitor jobs: running 21, waiting 39, completed 0, failed 2, total 62.
Import Monitor jobs: running 22, waiting 38, completed 0, failed 2, total 62.
Import Monitor jobs: running 22, waiting 37, completed 0, failed 3, total 62.
Import Monitor jobs: running 23, waiting 36, completed 0, failed 3, total 62.
Import Monitor jobs: running 24, waiting 35, completed 0, failed 3, total 62.
Import Monitor jobs: running 25, waiting 34, completed 0, failed 3, total 62.
Import Monitor jobs: running 26, waiting 33, completed 0, failed 3, total 62.
Import Monitor jobs: running 25, waiting 32, completed 0, failed 5, total 62.
Loading of 'DOKCLU' import package: ERROR
Loading of 'SAPAPPL1_1' import package: ERROR
Loading of 'DOKCLU~2' import package: ERROR
Loading of 'REPOSRC' import package: ERROR
Loading of 'REPOSRC~2' import package: ERROR
Import Monitor jobs: running 25, waiting 32, completed 0, failed 5, total 62.
Import Monitor jobs: running 25, waiting 32, completed 0, failed 6, total 62.
Import Monitor jobs: running 24, waiting 32, completed 0, failed 6, total 62.
Import Monitor jobs: running 24, waiting 32, completed 0, failed 6, total 62.
Loading of 'SAPAPPL1_3' import package: ERROR
Import Monitor jobs: running 23, waiting 32, completed 0, failed 7, total 62.
Import Monitor jobs: running 23, waiting 32, completed 0, failed 7, total 62.
Loading of 'SAPSSEXC_9' import package: ERROR
Import Monitor jobs: running 23, waiting 32, completed 0, failed 7, total 62.
Loading of 'DYNPSOURCE' import package: ERROR
Loading of 'SAPNTAB' import package: ERROR
Import Monitor jobs: running 20, waiting 32, completed 0, failed 10, total 62.
Loading of 'DYNPSOURCE~2' import package: ERROR
Import Monitor jobs: running 20, waiting 32, completed 0, failed 10, total 62.
Import Monitor jobs: running 20, waiting 32, completed 0, failed 10, total 62.
Loading of 'SAPSSEXC_2' import package: ERROR
Import Monitor jobs: running 19, waiting 32, completed 0, failed 11, total 62.
Loading of 'D010TAB' import package: ERROR
Loading of 'SAPAPPL2_3' import package: ERROR
Import Monitor jobs: running 17, waiting 32, completed 0, failed 13, total 62.
Import Monitor jobs: running 17, waiting 32, completed 0, failed 13, total 62.
Loading of 'SAPSSEXC_4' import package: ERROR
Import Monitor jobs: running 16, waiting 32, completed 0, failed 14, total 62.
Loading of 'SAPSSEXC_8' import package: ERROR
Loading of 'DD03L' import package: ERROR
Loading of 'SAPSSEXC_10' import package: ERROR
Import Monitor jobs: running 13, waiting 32, completed 0, failed 17, total 62.
Import Monitor jobs: running 13, waiting 32, completed 0, failed 17, total 62.
Import Monitor jobs: running 13, waiting 32, completed 0, failed 17, total 62.
Loading of 'DYNPLOAD' import package: ERROR
Loading of 'SAPSSEXC_6' import package: ERROR
Loading of 'SAPSDIC' import package: ERROR
Loading of 'SAPSLEXC_2' import package: ERROR
Loading of 'SAPAPPL2_1' import package: ERROR
Loading of 'SAPAPPL2_4' import package: ERROR
Import Monitor jobs: running 0, waiting 32, completed 0, failed 30, total 62.
Import Monitor jobs: running 0, waiting 32, completed 0, failed 30, total 62.
Import Monitor jobs: running 0, waiting 32, completed 0, failed 30, total 62.
Loading of 'SAPSSEXC_5' import package: ERROR
Loading of 'SAPSSRC' import package: ERROR
Import Monitor jobs: running 0, waiting 32, completed 0, failed 30, total 62.
Loading of 'SAPAPPL0_5' import package: ERROR
Loading of 'SAPAPPL0_2' import package: ERROR
Loading of 'DDNTF~2' import package: ERROR
Loading of 'DDNTF_CONV_UC~2' import package: ERROR
Loading of 'SAPSSEXC_7' import package: ERROR
Import Monitor jobs: running 0, waiting 32, completed 0, failed 30, total 62.
Import Monitor jobs: running 0, waiting 32, completed 0, failed 30, total 62.
Import Monitor jobs: running 0, waiting 32, completed 0, failed 30, total 62.
Import Monitor jobs: running 0, waiting 32, completed 0, failed 30, total 62.
Import Monitor jobs: running 0, waiting 32, completed 0, failed 30, total 62.
Import Monitor jobs: running 0, waiting 32, completed 0, failed 30, total 62.
Import Monitor jobs: running 0, waiting 32, completed 0, failed 30, total 62.
Import Monitor jobs: running 0, waiting 32, completed 0, failed 30, total 62.
Import Monitor jobs: running 0, waiting 32, completed 0, failed 30, total 62.
Import Monitor jobs: running 1, waiting 31, completed 0, failed 30, total 62.
Import Monitor jobs: running 2, waiting 30, completed 0, failed 30, total 62.
Import Monitor jobs: running 3, waiting 29, completed 0, failed 30, total 62.
Import Monitor jobs: running 4, waiting 28, completed 0, failed 30, total 62.
Import Monitor jobs: running 5, waiting 27, completed 0, failed 30, total 62.
Import Monitor jobs: running 6, waiting 26, completed 0, failed 30, total 62.
Import Monitor jobs: running 7, waiting 25, completed 0, failed 30, total 62.
Import Monitor jobs: running 8, waiting 24, completed 0, failed 30, total 62.
Import Monitor jobs: running 9, waiting 23, completed 0, failed 30, total 62.
Import Monitor jobs: running 10, waiting 22, completed 0, failed 30, total 62.
Import Monitor jobs: running 11, waiting 21, completed 0, failed 30, total 62.
Import Monitor jobs: running 12, waiting 20, completed 0, failed 30, total 62.
Import Monitor jobs: running 13, waiting 19, completed 0, failed 30, total 62.
Import Monitor jobs: running 14, waiting 18, completed 0, failed 30, total 62.
Import Monitor jobs: running 15, waiting 17, completed 0, failed 30, total 62.
Import Monitor jobs: running 16, waiting 16, completed 0, failed 30, total 62.
Import Monitor jobs: running 17, waiting 15, completed 0, failed 30, total 62.
Import Monitor jobs: running 18, waiting 14, completed 0, failed 30, total 62.
Import Monitor jobs: running 19, waiting 13, completed 0, failed 30, total 62.
Import Monitor jobs: running 20, waiting 12, completed 0, failed 30, total 62.
Import Monitor jobs: running 21, waiting 11, completed 0, failed 30, total 62.
Import Monitor jobs: running 22, waiting 10, completed 0, failed 30, total 62.
Import Monitor jobs: running 23, waiting 9, completed 0, failed 30, total 62.
Import Monitor jobs: running 24, waiting 8, completed 0, failed 30, total 62.
Import Monitor jobs: running 25, waiting 7, completed 0, failed 30, total 62.
Import Monitor jobs: running 26, waiting 6, completed 0, failed 30, total 62.
Import Monitor jobs: running 27, waiting 5, completed 0, failed 30, total 62.
Import Monitor jobs: running 22, waiting 4, completed 0, failed 36, total 62.
Import Monitor jobs: running 23, waiting 3, completed 0, failed 36, total 62.
Import Monitor jobs: running 24, waiting 2, completed 0, failed 36, total 62.
Loading of 'SAPAPPL0_1' import package: ERROR
Loading of 'ENHOBJCONTRACT' import package: ERROR
Loading of 'ENHOBJCONTRACT~2' import package: ERROR
Loading of 'SAPSSEXC_1' import package: ERROR
Loading of 'SAPAPPL2_5' import package: ERROR
Loading of 'SAPAPPL2_7' import package: ERROR
Import Monitor jobs: running 24, waiting 2, completed 0, failed 36, total 62.
Import Monitor jobs: running 24, waiting 2, completed 0, failed 36, total 62.
Import Monitor jobs: running 24, waiting 2, completed 0, failed 36, total 62.
Import Monitor jobs: running 24, waiting 2, completed 0, failed 36, total 62.
Import Monitor jobs: running 24, waiting 2, completed 0, failed 36, total 62.
Import Monitor jobs: running 24, waiting 2, completed 0, failed 36, total 62.
Loading of 'OCSCMPLOBJ' import package: ERROR
Import Monitor jobs: running 23, waiting 2, completed 0, failed 37, total 62.
Loading of 'SAPAPPL0_6' import package: ERROR
Import Monitor jobs: running 22, waiting 2, completed 0, failed 38, total 62.
Loading of 'SAPSSEXC_3' import package: ERROR
Loading of 'SAPAPPL1_2' import package: ERROR
Import Monitor jobs: running 20, waiting 2, completed 0, failed 40, total 62.
Import Monitor jobs: running 20, waiting 2, completed 0, failed 40, total 62.
Loading of 'SAPAPPL0_4' import package: ERROR
Loading of 'SAPSSEXC_11' import package: ERROR
Import Monitor jobs: running 18, waiting 2, completed 0, failed 42, total 62.
Import Monitor jobs: running 18, waiting 2, completed 0, failed 42, total 62.
Loading of 'SAPAPPL0_3' import package: ERROR
Import Monitor jobs: running 17, waiting 2, completed 0, failed 43, total 62.
Loading of 'SAPAPPL2_2' import package: ERROR
Loading of 'SAPPOOL' import package: ERROR
Loading of 'SAPSPROT' import package: ERROR
Import Monitor jobs: running 14, waiting 2, completed 0, failed 46, total 62.
Import Monitor jobs: running 14, waiting 2, completed 0, failed 46, total 62.
Import Monitor jobs: running 14, waiting 2, completed 0, failed 46, total 62.
Loading of 'DDNTT_CONV_UC~2' import package: ERROR
Loading of 'SAPUSER1' import package: ERROR
Loading of 'SAPDDIM' import package: ERROR
Loading of 'SAPDFACT' import package: ERROR
Loading of 'SAPDODS' import package: ERROR
Loading of 'SAPCLUST' import package: ERROR
Loading of 'SVERS~2' import package: ERROR
Loading of 'SAPUSER' import package: ERROR
Loading of 'SAPSLEXC_1' import package: ERROR
Loading of 'SAPSDOCU' import package: ERROR
Loading of 'SAPSLEXC_3' import package: ERROR
Loading of 'SAPAPPL2_6' import package: ERROR
Loading of 'DDNTT~2' import package: ERROR
Loading of 'SAPSLOAD' import package: ERROR
Import Monitor jobs: running 0, waiting 2, completed 0, failed 60, total 62.
Import Monitor jobs: running 0, waiting 2, completed 0, failed 60, total 62.
Import Monitor jobs: running 0, waiting 2, completed 0, failed 60, total 62.
Import Monitor jobs: running 0, waiting 2, completed 0, failed 60, total 62.
Import Monitor jobs: running 0, waiting 2, completed 0, failed 60, total 62.
Import Monitor jobs: running 0, waiting 2, completed 0, failed 60, total 62.
Import Monitor jobs: running 0, waiting 2, completed 0, failed 60, total 62.
Import Monitor jobs: running 0, waiting 2, completed 0, failed 60, total 62.
Import Monitor jobs: running 0, waiting 2, completed 0, failed 60, total 62.
Import Monitor jobs: running 0, waiting 2, completed 0, failed 60, total 62.
Import Monitor jobs: running 0, waiting 2, completed 0, failed 60, total 62.
Import Monitor jobs: running 0, waiting 2, completed 0, failed 60, total 62.
Import Monitor jobs: running 0, waiting 2, completed 0, failed 60, total 62.
Import Monitor jobs: running 0, waiting 2, completed 0, failed 60, total 62.
Import Monitor jobs: running 1, waiting 1, completed 0, failed 60, total 62.
Loading of 'SAP0000' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 0, failed 61, total 62.
ERROR 2014-02-24 21:22:38.964
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR 2014-02-24 21:22:38.995
FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_DB|ind|ind|ind|ind|0|0|NW_CreateDBandLoad|ind|ind|ind|ind|createdbandload|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|abapload|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR ( Last error reported by the step: Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.).
INFO 2014-02-24 21:22:39.463
Creating file C:\Program Files\sapinst_instdir\ERPEhP5\LM\COPY\ORA\SYSTEM\HA\AS-ABAP\DB\__instana_tmp.xml.
INFO 2014-02-24 21:24:32.178
An error occured and the user decided to stop.\n Current step "|NW_ABAP_DB|ind|ind|ind|ind|0|0|NW_CreateDBandLoad|ind|ind|ind|ind|createdbandload|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|abapload|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor".
INFO 2014-02-24 21:24:38.137
Working directory changed to C:/Program Files/sapinst_instdir/ERPEhP5/LM/COPY/ORA/SYSTEM/HA/AS-ABAP/DB.
INFO 2014-02-24 21:24:38.153
Creating file C:\Program Files\sapinst_instdir\.lastInstallationLocation.
How to convert a text file to audit file,MD5(.aud) in sap-abap?Please provide me the code if possible.
Hi,
For our project we are working on RUBY + NSRFCSDK.
We have download the Linux x86_64 bit version.
As Ubuntu and Mac both works on Linux and Unix base so we have expected that nwrfcsdk will work with the OS
During installation process when we have followed these steps:
ruby setup.rb config --with-nwrfcsdk-dir=/usr/sap/nwrfcsdk
ruby setup.rb setup
We are getting various errors.
In Ubuntu even Cofing command fails
Where as in Mac it completes the Config, however it fails on SETUP step and it shows this error
setup.rb:658: warning: Insecure world writable dir /usr/local in PATH, mode 040777
linking shared-object nwsaprfc.bundle
ld: warning: ignoring file /usr/sap/nwrfcsdk/lib/libsapucum.so, file was built for unsupported file format which is not the architecture being linked (x86_64)
ld: warning: ignoring file /usr/sap/nwrfcsdk/lib/libsapnwrfc.so, file was built for unsupported file format which is not the architecture being linked (x86_64)
We have tried all possible ways and problem is coming with libsap files. Because it creates a nwrfcsdk.bundle for ruby which application is not able to load due to failure of libsapucum.so and libsapnwrfc.so
Please respond as soon as possible. That would be really helpful.
Thanks
Shivani
Dear experts.
i am trying to create some rules regarding the outgoing message.
For instance: if the subject of the email contains the word "prevent" to do not send the email.
Tipical rules just like the outlook.
Is that possible with the SAP connect? Many thanks in advance.
Dear colleagues,
I am using IDoc for maintenance of material master records. It's basic type is standard MATMAS05. When I trigger IDoc that needs to change material master record, this material master record is updated correctly, except AENAM field (Name of accounting clark who changed record). In my IDoc structure I have field which defines AENAM. This field is filled with proper information, but after IDoc running ERP MARA-AENAM is filled with logon user defined in RFC Destination settings and not with value from IDoc's AENAM.
Could you help me to solve this issue and have proper data in MARA-AENAM (from IDoc AENAM field)?
Regards,
Harry
Hello Friends,
I have to change the Idoc record type version in Port setting from Release 3.0/3.1 to Release 4.1.
Could you let me know what all changes need to be taken care during this process?
What would be the Impact on Inbound and outbound process?
Hello,
I am trying to retrieve the field names of internal table itab using FM 'GET_COMPONENT_LIST'
Executing the function module in se37 for my program and itab, I get the fieldnames in COMPONENTS table.
But when using it in report ztestv, COMPONENTS is empty.
I tried to search the forum and carried out the steps as mentioned, but didn't find any solution.
Following is my code:
-------------------------------------------------------------------------------------------------------------------------------------------------
REPORT ZTESTV .
data: begin of itab occurs 0,
NAME1 type string,
age type i,
amt type i,
end of itab.
DATA : work_area LIKE LINE OF itab.
data: wa_csv_out type table of string.
itab-name1 = 'AAAA'.
itab-age = 20.
itab-amt = 120.
append itab.
itab-name1 = 'BBBB'.
itab-age = 40.
itab-amt = 150.
append itab.
itab-name1 = 'CCCC'.
itab-age = 25.
itab-amt = 400.
append itab.
DATA: lt_comp TYPE table of RSTRUCINFO,
ls_comp TYPE RSTRUCINFO.
CALL FUNCTION 'GET_COMPONENT_LIST'
EXPORTING
PROGRAM = sy-repid
FIELDNAME = itab
TABLES
COMPONENTS = lt_comp.
LOOP AT lt_comp into ls_comp.
append ls_comp-compname to wa_csv_out.
ENDLOOP.
-------------------------------------------------------------------------------------------------------------------------------------------------
Please help.