This is the right answer and the explanation clearly articulates the rationale.
↧
Re: Classification with LSMW RCCLBI03 (DI): Cannot update BIAUSP-LKENZ
↧
Abap client proxy
All,
I have created a client proxy in CRM system and i have tested in from SE80 and everything works i retrieve data and works fine.
But now i have created a test program where i use a client proxy and i send the request with the same parameters, but i do not receive any response.
I have created the proxy object with the logical port and no exception is being throwed, any idea?
Regards
Jon
↧
↧
Interesting DELVRY03 SHPCOND problem
Dear experts ,
I am trying to change delivery update using DELVRY03 and message thpe SHPCOND.
Below segments been populated below:
(1)
E1EDL20
VBELN 0072029903
VSTEL FNU1
VKORG DIL
(2)
E1EDL24
POSNR 10
MATNR FT13320H
(3)
E1EDL37
EXIDV FT13320H
VHILM 000000001227010095
(4)
E1EDL44
VELIN 1
VBELN 0072029903
POSNR 10
EXIDV FT13320H
VEMNG 2
VEMEH CS
I am not able to prevent this error coming because of VHILM field in (3).
1227010095 does not have packaging material type and is therefore not a pack.mat
How can i prevent this ?.This is a packaging material as per master.
We in our company are not using standard packaging material type VERP but some 'IPAM'.
Infact why idoc generation logic is triggering Handling unit to be filled in segments.
Any addon will be a great help for me,totally bamboozled.
Looked on some similar threads ,tried to imitiate same actions but not working.
Regards.
Aditya Sharma.
↧
Re: Interesting DELVRY03 SHPCOND problem
do you get the same error when you change the delivery in VL02N?
↧
Re: bapi extension in lsmw bapi method
Hi,
I know that this tread is old, but I want to post something that can help those who search on scn:
Check below link, it may be helpful for you.
Regards.
↧
↧
Electronic data interchange- edi
I read that SAP has defined its own edi standard known as idoc.
But i am not finding any articles on the web nor in scn where i can get the design history of idoc.
I mean whats the difference between standards like x12 ans idoc.Why is idoc considered better?
Can somebody please help me understanding this?
It has been one week i am looking for this information.
Thank you very much beforehand.
↧
Re: SHPMNT iDoc - "Vehicle" field not available
Hello Daniele,
If you don't want to go to Idoc extension , you can try reusing any field from segment E1EDT20 to populate the Vehicle information.
But first make sure that field is not going to be used in your business scenario.
Like there are two External ID field in idoc, if business is going to use only one of them then second you can use for vehicle purpose.
↧
Re: Object Classification BAPIs and buffering?
Hello Markus, I do not have a direct answer to your question but we are using BAPI_OBJCL_CHANGE. The BAPI itself expects the final classification values in the parameter ALLOCVALUES*NEW. In the BAPI itself classification values not available in the input table will be deleted and values that are not yet existing will be created.
Is it possible for you to combine the 3 mentioned BAPI's and just call the *CHANGE* BAPI ?
Regards Jack
↧
Re: Electronic data interchange- edi
Hi Nousha,
ALE is technology for SAP mainly used to transfer data between SAP systems.
EDI is the independent technology use to transfer data between two systems, they can be SAP systems or non SAP systems.
The basic difference with ALE and EDI is ALE used for internal communications and EDI is meant for external communications.
Since ALE uses an IDOC format to exchange data between systems, both participating systems should understand the IDOC format.
In other words ALE normally used to distribute the master data (Ex: Material Master, Vendor Master) with in a company when you are maintain the distributed
environment. EDI is for exchanging transaction data (Purchase order,
Delivery) between two different business partners.EDI is all about the standards (Ex: ANSI X12, EDIFACT) you have to follow when you are transferring business documents. Technically speaking, ALE transfers the data using memory
buffers whereas EDI uses file port to transfer the data.
With EDI technology you always need a translator to convert the IDOC to X12 (Outbound), X12 to IDOC (Inbound).But with ALE you don’t need a translator.
Check out this page: http://wiki.scn.sap.com/wiki/display/ERPLO/Structural+relationship+between+IDoc+and+EDI+Standard+messages+for+SD
Regards.
↧
↧
Are Import parameters compressed in external JCo RFC calls?
I would like to send XML data from a Java program to an SAP ABAP System running on NW 7.02.
The connection is done by Java Connector 3.0. The XML file should be passed as a parameter of an RFC function module.
In older versions the data would have been passed as a TABLES parameter and would be compressed automatically if the payload exceeds 8kb or the connection would be marked as a slow connection. (see also Note 977407).
Now I would like to use the basXML RFC protocol. There it is advised to use Table Types in Import parameters instead of TABLES parameters for table data. Now will the data be compressed if I send them as Table data in an Import parameter? And will they also be compressed when I send them as an Import parameter as STRING or XSTRING instead of a table?
Unfortunately the help documentation is incomplete on these topics and I did not find any details for this scenario.
↧
Re: Electronic data interchange- edi
oh...this is so helpful
but still i have the question: we could have used x12 or edifact instead of creating another technology right??i mean even for the ALE...we could have use the x12 or any existing at that time...
because from the website you gave me, it seems that idoc can do the same thing as edifact etc...
we could have reused these standards right?instead of inventing another one....
thank you very much....every sentences have been very helpful...it helps to read further...
↧
Re: Electronic data interchange- edi
Nousha,
it is a question of standards. The structure of an IDoc is defined by an IDoc type. Among other things, the IDoc type contains information about which data is saved where (line and offset), The IDoc type is assigned to the message type. Whereas the message type contains only the semantics of the message (for example, material master data), the IDoc type contains the exact structure of the document for a message type. This means there can be different versions of a material master IDoc, for example, each with a different IDoc type. This enables versioning, which means that IDoc scenarios can be developed further in a compatible way.
Check out the preview of this edi book from sap press which has a scenario of an inbound edi X12 850 PO to ORDERS IDoc interface: https://www.thali.ch/files/Shop/Documents/013603_Leseprobe.pdf
Hope that solves your issue.
↧
SAP ECC6.0 Scheduling Jobs for MATMAS
Hello gurus,
We have scheduled a background job in order to send idoc type MATMAS if any material has changed, or newly created.
Even though the job works, we need to also be able to send the material's characteristics.
These characteristics were not available before MATMAS05.
In the case that we send the material via BD10, it is sent in full, but we need the background job to also send them in full, since there are too many materials created every day.
Is there a way to add these fields in the job?
Thanks in advance!
↧
↧
Re: Electronic data interchange- edi
Hello,
yes i guess...you said it right...it is a question of standards...any firm decides about the appropriate standards they find suited to their application..
however, i still have questions in my mind...haha....but dont worry...i shall look for the information by myself...as you already gave me a starting point....
thank you very much...
just to share my knowledge: yesterday i learnt that idoc is based on x12 and mostly on edifact...they had tried to merge both the goodsides from x12 and edifact together with the IDOC technology...
hence, i guess they did not invent another wheel....
indeed a good relief...lol...
but still need to know more...
indeed you have been very helpful to me...
if you find some more links related to the history of idoc...i would be grateful to you if you could send them to me...thank you very much....
bye
↧
why ADODB.connection can not be used in background?
hi all :
i have a problem.
i can run it in se38 and it's successful , but i cannot run it in background, can not use it in sm36, the data are not be inserted into sqlserver2008, and there are not any error messages.
could you help me ? thank you.
"-----------------------------------------------------------------------------------------
CONCATENATE
'Provider=' 'SQLOLEDB' ';'
'data Source=' p_ip ';'
'Initial Catalog=' p_conname ';'
'User Id=' p_name ';'
'Password=' p_password
INTO connstr.
CONDENSE connstr.
……………………………………………………
CREATE OBJECT cn 'ADODB.connection'.
CALL METHOD OF cn 'OPEN'
EXPORTING
#1 = connstr.
sql = ' INSERT INTO T1( AAA) …………………………'
CALL METHOD OF cn 'EXECUTE'
EXPORTING
#1 = sql.
IF SY-SUBRC = 0.
COMMIT WORK.
ENDIF.
from china.
↧
Re: BAPI_BUPA_ROLE_ADD_2 - Add role To partner
Actually i also face the same problem that Santosh Banupanth was facing...... still its not working.... i dono wat is the problem...if somebody knows please to help me.....
↧
Re: why ADODB.connection can not be used in background?
Hello Jin Pan
The ABAP statements 'CREATE OBJECT' and 'CALL METHOD OF' use OLE automation on a (Windows) sapgui client. When you run a program in background it is executed directly on the SAP backend and there is no connection to a client computer. The SAP backend might even not run on Windows but on another operating system that doesn't support OLE automation. But even when it is these OLE statements only apply to client computers.
When you need to connect to a database in background you need another solution then OLE automation. Solutions like DBCON or UDConnect.
Regards Jack
↧
↧
Re: Object Classification BAPIs and buffering?
Hello and thanks for your interest! 
As you can see from the date this was quite a few years ago and I have changed company several times since then.
If memory serves me correctly we did the "quick & dirty" solution of committing after the BAPI_OBJCL_DELETE and then performing the BAPI_OBJCL_CHANGE or BAPI_OBJCL_CREATE.
Not an elegant solution but it worked. Hope this helps. As always please check SAP notes to see if anything has changed in this area in the last 4 years! 
Kind Regards,
Markus
↧
Can you please guide me on the following scenario
HI,
Can you please guide me the following scenario as I am new to SAP PI.
How to transform IDOC to Excel Sheet and that excel sheet send via mail to concern customer
Thanks in advance
Kallu
↧
Create 2 outbound Idocs for 1 message type
Hi Experts,
We are sending an outbound Idoc of message type DESADV. We would like to trigger 2 Idocs per Shipping Notification.
Could you please help?
Thanks,
Vitish.
↧