Reg : Type changes in Idoc
Hi Frens,
There are some characteristic value exists for material.
Characterstic values are in numc , date , time format.
But ir stores in CAWN table in Internal floating point format.( field : ATFLV )
when issuing output , I am getting the same Internal floating format data in idoc also.
I am checking the E1cucfg segment.
But data should be in Date , Time , Numc format..respectively depending upon the characteristic value .
I am using order_output_ordrsp function module.
how to rectify it.
Needed help
Your config values are fetched in the call to FM CUXI_GET_MULTI_CONFIGURATION in the form <i>call_kmat_to_idoc</i>. Debug this function module to see why it is not converting your values into external format.
If that is not possible then right after the call to the above function module, there is a user exit where you can manipulate the values of the internal tables containing your config data. In that user exit, you put your logic to convert them from internal floating point format to external format.
*- Customer function to change the internal tables for ----------------*
*- configurable materials ---------------------------------------------*
CALL CUSTOMER-FUNCTION '006'
TABLES
dh_appl = h_appl
dcuref = curef
dcucfg = cucfg
dcuins = cuins
dcuprt = cuprt
dcuval = cuval
dcublb = cublb
EXCEPTIONS
error_message_received = 1
data_not_relevant_for_sending = 2.
Similar Messages
-
Issue in transporting changed material type using ALE-IDOC
Hi All,
I am sending the material master data from one system to another using ALE-IDOC.The issue is that teh material type is not getting sent from one system to another after changing the material type.I mean the changes in material type are not getting updated.I will be indeed thankful if anyone can guide me resolve this issue.
Thanks.Hi,
Not all the fields that are changed in material master are sent in the Idoc. Material type is one such field.
Create change pointer on some other field ex. net value or material desc. and transfer the material type changes under it.
KR Jaideep, -
How to chang the idoc message type
Hi,
I want to change the idoc message type...because the idoc has the status 51...pls advice how to change
I have tried it from we81 .......but i cant open the msg type ...when i double click on it.
Regards,
SomenathHi,
This may help u
Steps To Create Custom IDOC
1.Create Segment Type (WE31)
Go to Transaction code WE31
Enter Segment type, click on Create
Give Description
Enter the Necessary Fields & Data Elements for those Fields.
Save the Changes.
2.Create Idoc Type (WE30)
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
3.Create Message Type (WE81)
Go to transaction code WE81
Change the details from Display mode to Change modenAfter selection, the system will give this message u201CThe table is cross-client (see Help for further info)u201D. Press EnternClick New Entries to create new Message Type
Fill details
Save it and go back
4.Assign Idoc Type to Message Type (WE82)
Go to transaction code WE82
Change the details from Display mode to Change moden After selection, the system will give this message u201CThe table is cross-client (see Help for further info)u201D. Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Regards
Seshagiri -
Creation of New Message Type for Extended IDoc
Dear Friends,
I want to create New Message Type for MATMAS and want to Active Change Pointers accordingly. Thru this Message Type how can I able to use Extended IDoc which I have created for Basic Idoc Type MATMAS05.
I am Sending Data from SAP to XI ; Any one can help me in this How can I create the Message Type with the IDoc Extn .
for Change Pointers.
Warm Regards,
Naveen Mutyapu.Hi naveen mutyapu,
see these links
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
http://www.allinterview.com/rss/interview-questions/new/SAP-ALE-IDocs.xml
happy learning.
thanks
karthik -
Mapping every record in a given message type to an IDoc
Hi all,
As per the requirement, I have a message type which stores a number of records from the database. The root node of the message type repeats as many times as the number of records. I need to map this message type to an IDoc with an IDoc created for each record. However, the pre-defined structure of IDoc has the root node occuring only once. Can the mapping of every record to an IDoc be acheived by using Message tab of the message mapping to have the IDoc occurence as 0..unbounded?
Thanks,
AmitHi,
In message mapping Change the occurence of the IDOC as 0 to unbounded in the Target message inside Messages Tab.
Also change the occurrence of IDOC in the Interface mapping as 0 to unbounded.
Thanks,
Tiny
Edited by: TINY MAMPILLY on May 7, 2009 11:14 AM -
Hi Gurus
Can anyone help me in sending the changes for the IDOC for transactional data.
For Sales Order IDOC -- ORDRSP.
When newly sales order is created, all the sales order information should be sent. --This is not a problem.
When changes are done on the sales order -- Only the changes should be sent in the IDOC. I have activated the change pointers in BD50, BD51 for ORDRSP and in BD52 created the entries for ORDRSP.
but when i trigger the IDOC using the output type, i get to see all the data instead of only the changes.
Is there anything that i am missing???
Any help is really appreciated.
Thanks
SarithaHi Linda,
I have documentataion on ALE/IDOCs which may not be helpful to you. If u need that i can send u .
Instead i can help u out if u r facing any issue.
In our case: wen ever sales order is created /changed an idoc shud be genrated.
This can be done thru Message control.
Which involves customization from functional guys in NACE as well as Technical guy in Partner profile/port..
do let me know where ever u r not clear.
regards,
Naveen -
Posting goods issue using Message type SHPCON and idoc type DELVRY03
Hi SAP Gurus,
I am using message type SHPCON and idoc type DELVRY01 with processing code DELV to post goods issue for a delivery note.
I tried to simulate the inbound entry via WE19. The scenario should be posting goods issue based on the delivery order.
In some cases, quantity issued is less than the quantity in the DO. For this, I need to change the delv quantity in the DO via VL02N before I select Post goods issue button. This will change at the same time post the goods issue.
What I have filled up are the fields:
E1EDL20-VBELN = DO num
E1EDL20-VSTEL = Plant
E1EDL18-QUALF = "PGI"
E1EDTH13-QUALF = "006"
E1EDTH13-NTANF = date today
E1EDL24-POSNR = 000010
E1EDL24-MATNR = material num
E1EDL24-WERKS = delv plant
E1EDL24-LGORT = sloc
E1EDL24-LFIMG = updated quantity
But everytime I simulate using WE19, the entire quantity in the DO is not changed at all. The goods issue quantity posted is still the original DO quantity.
May I know how to do this? Thanks.Put value in E1EDL24-LGMNG for qty to pgi.
-
How I can identify the various message types that are been plugged in an IDOC Type? What will be the Transaction Used to identify that? I used the Transaction WE30, but I see the various segments that are been attached to the IDOC type and Not at the Message Type level. I used the IDOC type ORDERS02.
SAP uses a single IDOC type for several logically related messages. For example, the Orders IDOC type (ORDERS02) is used for several messages, such as Order (ORDERS), Order Response (ORDRSP), and Order Change (ORDCHG).
Create Message Type WE81
Create IDOC Type WE30
Assign Message Type to IDOC Type WE82
Can some one please help me? Appreciated.
,JYou can check this in the table EDIMSG.
Alternatively you can check this in WE82 as well:
WE82 --> Menu func. 'Selection' --> By Contents --> Select "By Contents" --> I/P your basic type & select "choose"
This will give you the list of the basic types associated with the message types.
Edited by: Suhas Saha on Jun 23, 2010 6:40 PM -
Multiple message types for an idoc type
Hi all,
I created one custom idoc type with six segments. I heard that one idoc type can have any number of message types
if it is so pls tell me how to assign these two message types for my idoc .
i want to create multiple message types because i want to send same idoc type to diff legacy systems.
My requirement is message type one is only for first three segments and message type two is for another three segments .
The outbound program 1 for mess type 1 should fill fill the data for only first three segments and second outbound program corresponding to mess type 2 should fill the data for last three segments
how should i design for my requirement. suppose if the idoc has two message types then it has two outbound programs?Hi Kunal,
Below are my thoughts from a design perspective,
My requirement is message type one is only for first three segments and message type two is for another three segments .
The outbound program 1 for mess type 1 should fill fill the data for only first three segments and second outbound program corresponding to mess type 2 should fill the data for last three segments
Before you look upon the no. of message types you need, i guess you need to look at the business requirement. Per your requirement you want to send send two sub sets of data. The first subset in the first 3 segments and other three segments for the second subset of data.
Is the structure of the first subset of data similar to the second subset If not, better to create two IDOC Types. If they are similar, then create one IDOC Type with three segments and have two message types for each subset of data.
For Ex: ORDERS05 is the IDOC type for Orders, this IDOC type provides capability to carry data related to any type of orders
but the action on the data is facilitated by the message type like ORDERS for create, ORDCHG for change, ORDRSP for Order response etc.
OR
Are these two subsets of data related to each other, if yes understand the relation? If not related at all then you might be better of creating two separate IDOC Types.
Like in the above example A purchase order is related to a sales order so you can use the same IDOC type, but in case of a order response and ASN that data sent is different and hence you will need different IDOC types (even though a SO is related to a DN).
how should i design for my requirement. suppose if the idoc has two message types then it has two outbound programs?
The above again depends on the how tightly/loosely coupled are the data sets, you can have just one program and have a simple case statement on the message types or have two different programs.
You will also have to consider points like, if any of the subsets is more prone to more change in terms of the structure and associated business logic. If yes, then you might want to keep the programs separate to reduce work on regression testing etc.
I am sure you will receive more inputs from the experts on the forum and the list of points to look for will get longer , so understand the requirement, dependencies and if you have any specific questions you could post it on the forum.
Regards,
Chen -
Message Types in DELVRYxx IDocs
Can anyone tell me why SHPORD/WHSORD/SHPCON/WHSCON message types apply for idoc DELVRY03 but not for DELVRY05? I thought each new version of the IDoc would still be used for the original message types.
Thanks,
KeithMaybe because of some problems. For example : [Note 971803 - No IDoc object types for SHPCON and WHSCON|http://service.sap.com/sap/support/notes/971803].
But I found no proof of this change! Normally it can't be changed without a note (I mean, without informing).
For information, this note created the messages : [Note 311664 - Assignment of IDoc type DELVRY02 is incomplete|http://service.sap.com/sap/support/notes/311664]. -
Modifiy a generated IDOC (basic) type - HOWTO REGENERATE IDOC?
Hi there!
I have a basic IDOC type, i can unrelease this type but when I try to edit the (also unreleased) Segment, he says:
<i>"Segment type Z1Z8_INTERFACE_CRM cannot be changed"
Detail:
Message no. EA 667
Diagnosis
Segment type Z1Z8_INTERFACE_CRM is flagged as generated.
System Response
Generated segment types can only be displayed.</i>
So the main question is:
<b>How to maintain/modify a generated IDOC segment?</b>
(I think i have to re-generate a new one??)
If i try to edit the complete Type in WE30 he says:
<i>Z8QM_CHECK_CRM0001 generated, only display possible
Message no. E0 665
Diagnosis
Z8_CHECK_CRM0001 was created (generated) automatically, not interactively.
System Response
Generated objects cannot be changed via the IDoc type editor, only displayed.
Procedure
If you want to change Z8_CHECK_CRM0001, you must generate it again. Contact the person responsible. For their name, select Goto -> Header data from the editor display,</i>
And my problem is: I cannot contact the resp. person ...I'm sorry, I haven't got an email notification for this thread. Here's your reply (I think it is to late, but....):
Important for backward compatibility: When changing the IDoc structure, it is recommend to append new fields at the end of the current structure. Also it is not recommend to change current fields (data type, length).
*To add fields to the IDoc structure/segment, maintain it's base-structure. Remember to save and activate changes to Structure.*
Note: The structure is a simple structure (dictionary object) within the segments' development class (for the name of the development class, see segment attributes in transaction WE31). In my case it's name was Z8ABC and the segment-name was Z1Z8ABC.
Use Transaction "BDBG" (or "BDFG") to re-generate the IDoc Structure for the Methods "ABCD" and "EFGH" (Interface type: Z8_ABCD).
To re-generate, follow this steps:
- Cancel release
-- Menu "Edit" -> "IDoc type and segment type" -> "Cancel release"
- Update segments
-- On main screen, enter "interface type" and "method name"
-- Click "Edit" which opens the parameters screen
-- On the parameters screen, click "Continue"
--- An information is displayed, that the segment was updated
- Release objects again
-- Menu "Edit" -> "IDoc type and segment type" -> "Release"
Repeat for all methods using this structure. To check the new structure use transaction ?WE30?. -
Trying to change Inbound IDOC to Outbound IDOC for testing....
Hi Friends,
I am trying to do the following
1) In our legacy system SAP R/3 3.1H we have received an IDOC from our partner. This has been stored correctly.
2) We now need the same functionality in our SAP R/3 4.6C system so I have created the IDOC type + segments accordingly. I have also set up the partner profiles
3) We need test data but our partner can not send yet so the only other way is to send this INBOUND IDOC from 3.1H to 4.6C.
4) HOWEVER, i have tried everything to do this like using WE19 to edit the idoc, but I can not process it for OUTBOUND processing.... You can in 4.6C but there is no option in 3.1H.
HELP!! RewardsHi Friend,
The test programs allow you to skip certain sections of the processing chain between applications to localize errors. However, they can also be used to simulate an entire business process (for example, purchase order on the customer side with posting of the purchase order on the vendor side) in an SAP System (without any other systems). For this reason, the test programs are an important tool for configuring the IDoc Interface and defining new IDoc types.
Use
You can use the test tool to generate an IDoc manually and send the IDoc for either inbound or outbound processing. You are not restricted to a specific port type. You can start with an IDoc type (an empty IDoc) or use an old IDoc as a template and edit the IDoc, that is, add segments or change data. This is a good way to test new IDoc types, in particular.
You can forward your new IDoc for standard inbound processing (checking partner profiles and so on). You can also call a function module directly. You can therefore test new function modules for new IDoc types.
Activities
· Start the test tool with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Test Tool (WE19). You can use a template for your test IDoc.
You can choose IDoc types as a template, either directly or according to a specific message type. You can use the F4 Help for IDocs used as a template, which searches for IDocs by selection criteria, in the same way, for example, to IDoc Display. When an IDoc file is used as a template, the IDocs are read from this file and are available to you for selection. A default value for the IDoc file gives you the system using your test port which you can enter in IDoc Administration . This test port must therefore be of the file type. The default file is the inbound file entered there.
· You generate the IDoc using .
The IDoc is displayed as a tree structure. If you do not use a template to create the IDoc type, at least one more segment must be added.
· To create segments in the form of tree nodes (colored fields) place the cursor on an existing node (for example a control record at the top) and choose .
You can cut, paste or copy individual segments or entire segment groups by positioning the cursor on the relevant segment and selecting the required action from the Edit menu.
· Click on the white fields to change data in the segments.
In the case of the control record, only the fields which are relevant for standard inbound processing are displayed. Do not forget the required entries in the partner profiles if you want to send the IDoc for standard inbound processing! You can also change all of the control record data by choosing All fields in the edit screen.
In the All fields editor screen you must enter the non-language specific partner function (for example AG for vendor). This is the only screen in the IDoc Interface in which the partner function is not translated into your language (in English AG becomes vendor VD) - in the partner profiles or in the IDoc display the field is always translated. Thus, you see the partner functions here in the way they are saved in the database. This is a unique value in the SAP System and therefore protected against mistakes.
· The additional procedure depends on whether you want to test inbound or outbound processing.
Test: Outbound Processing from MC
Use
Use this test program if you have chosen the Message Control module and want to test generation of an outbound IDoc from an existing message status record (table NAST).
Prerequisites
You must be able to post the application documents which are to be converted into IDocs by the Message Control module correctly so that a message status record can be generated. In the case of the Materials Management (MM) and Sales and Distribution (SD) components, the following entries are required:
· Customer or vendor records
· Material records
· Info records
· MC condition record: The output medium 6 (for EDI) must be entered here. The condition records are maintained as messages from the respective application.
The appropriate file ports and partner profiles must exist in the IDoc Interface.
Outbound processing must be stopped when the message status record has been generated to allow the test program to intervene. To do so, you must set the Message Control dispatch time to 1 (output with selection run) in the corresponding condition record in the application. This test program, therefore, is simply used to start a selection run which retrieves the Message Control records and sends them for further outbound processing. The program is report RSNAST00, which is also generally scheduled with dispatch time 1 in live operation.
Activities
Once the application document has been posted, outbound processing stops after the message status record has been generated and is triggered again by the test program. Choose SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Outbound ® Outbound from MC.
Errors are stored in the Message Control processing log (document header) and in the status records of the IDocs. The status records, however, are only available if the IDoc was successfully generated.
Use
This test program selects one or more outbound IDocs and forwards them to the external system. You can choose the IDocs according to various criteria (for example, recipient or business message).
Prerequisites
You require outbound IDocs which were generated without errors (no error status). The partner profiles, therefore, must be maintained completely.
Outbound processing must stop when the outbound IDocs have been generated to allow the test program to intervene. You can check this by setting the output mode to Collect IDocs in the partner profile for the IDoc Interface. If you now generate an outbound IDoc for the partner (for example, using the application or the test tool), the IDoc is only generated in the SAP System and is not forwarded to the external system. This test program, therefore, is simply used to start a selection run which retrieves your IDoc(s) and sends them to the external system. The program is report RSEOUT00, which is also generally scheduled with the output mode Collect IDocs in live operation.
Activities
You start the test program by choosing SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Outbound ® Outbound from IDoc (WE14).
You can decide whether the output mode is set to Start subsystem or Do not start subsystem in the partner profile. This defines whether the external (sub) system processes the IDocs further.
Use
This program is used to test whether status confirmations for an outbound IDoc are sent correctly from the external system to the SAP System. The port type here must be set to File.
Prerequisites
A correct status file which can be generated by an EDI subsystem, for example, is required. The status file must refer to an existing outbound IDoc in the SAP System. You can also generate such a status file yourself.
The sender port must be recognized by the receiving system. The port must therefore be maintained as a port of type File in the port definition for the IDoc Interface. The entry for the inbound file must also be given here.
Features
The SAP System reads the status file. The IDoc number contained in the file refers to the outbound IDoc, to which the status confirmation relates. The confirmed statuses are credited to the relevant IDoc in the form of status records in the SAP System.
Activities
Start the test program with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Status ® Edit Status File (WE17) and pass the inbound port, name and directory of the file. These entries overwrite the standard values which you have stored in IDoc administration using the test port.
Test: Inbound Processing: Modified Outbound File
Use
This program converts an outbound file with IDocs to a correct inbound file and sends the new file for inbound processing. The outbound file is not modified and can therefore be used more than once. The port type here must be set to File.
Prerequisites
You need a correct outbound file, for example, a file which is generated by the test tool or using a standard outbound processing. In this case, a port of the type File must be specified in the partner profile for the IDoc Interface, so that the IDoc(s) can be written to a file.
The sender port must be recognized by the receiving system. The port must therefore be maintained as a port of type File in the port definition for the IDoc Interface. The entry for the inbound file must also be given here.
Features
The program imports sender and recipient data as input parameters from the user. The program reads the IDoc file and changes the corresponding entries in the IDoc control record. The changed data is written to a second IDoc file at the operating system level.
Standard inbound processing is then triggered;
· Reading the modified file
· Generating the IDoc(s) in the SAP System
· Processing in the application
Activities
Start the test program with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Inbound ® Inb. Mod. Outb. File (WE12).
Set the sender and recipient data, as well as the outbound file and the inbound file to be generated (path and name). Your entries for the inbound file overwrite the standard values which you have stored in IDoc administration.
The recipient in this case is the SAP System. The port is used for identification purposes:
· SAP (for example RSMITH
Test: Inbound Processing: Original Inbound File
Use
This program reads an inbound file and sends the file for inbound processing. If all data has been successfully read, the file is deleted.
Prerequisites
You require a correct inbound file. In this case, correct means that the:
· Sender and recipient in the control record are correct
· Direction in the control record is set to 2 (inbound)
· Client in the control record and data records are correct or empty
The sender port must be recognized by the receiving system. The port must therefore be maintained as a port of type File in the port definition for the IDoc Interface. The entry for the inbound file must also be given here.
Features
The program reads the IDoc(s) from the inbound file and sends them for standard inbound processing (with processing within the application).
The file is deleted after being read successfully!
Activities
Start the test program with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Inbound ® Inb. Orig. Inb.File (WE16) and pass the following data:
· Inbound port
· Name and directory of the file
These entries overwrite the standard values, which you have stored in IDoc Administration using the test port.
Thanks -
MRP type change from VB to PD - Problem in old requirements MD04
Hello Experts,
For MRP run we were using VB as MRP type in material master. We upload schedule in scheduling agrrements. At time of MRP run system was only considering based on reorder point only.
Now business disicion is change and we have changed MRP type as PD. So at time of MRP run system should consider based on requirements i.e. from scheduling agreement. Now here is our problem. System consider and shows old scheduling requirement also in MD04. Let me explanin you in detail. Before changing MRP type from VB to PD, there were some schedule available in system. after that we have uploaded 2 3 more schedule. But system still shows old schedule availabe at time of MRP type change.
Can you please help me how to resolve this?? How can we clear old requirements from system.
Thanks in advance for your reply.
Regards,
PiyushHi,
Not too sure but , try # SDRQCR21
Regards
Chandrasekhar -
Receiver AS2 Advantco Adapter Content type change
Hi All,
I am working on SFTP to As2(Advantco) scenario. We are sending the txt files to target.
As of now file is sent with content type application/xml. But target system is asking to change it to "application/octet-stream"
In the AS2 adapter guide, there is section 3.4.4.8. MIME Settings which talks about content type change.
Unfortunately i am not seeing that in the receiver channel.
does anyone know how to change the content type for AS2 channel?
Will standard adapter module work on third party adapter? like messageTransformBean
Thanks.This could be because of adapter metadata is not updated one?
>>> Yes. It's very much possible.
Will standard adapter module work on third party adapter? like messageTransformBean
>>> AFAIK - Advantco adapters does support MTB. -
How to find the Column data type changes in table
Hi All,
I need to find out the column data type changes where made recently in table .
How do i check past changes in column data type. Any data dictionary are there to find out the data type changes in the column .
Thanks in advance..<FONT FACE="Arial" size=2 color="2D0000">
You have the answer on hand (user_arguments / all_arguments)!
SQL> desc user_arguments
Name Null? Typ
OBJECT_NAME VARCHAR2(30)
PACKAGE_NAME VARCHAR2(30)
OBJECT_ID NOT NULL NUMBER
OVERLOAD VARCHAR2(40)
ARGUMENT_NAME VARCHAR2(30)
POSITION NOT NULL NUMBER
SEQUENCE NOT NULL NUMBER
DATA_LEVEL NOT NULL NUMBER
DATA_TYPE VARCHAR2(30) --> Data Type
DEFAULT_VALUE LONG
DEFAULT_LENGTH NUMBER
IN_OUT VARCHAR2(9) -->Argument direction (IN,OUT,or IN/OUT)
DATA_LENGTH NUMBER
DATA_PRECISION NUMBER
DATA_SCALE NUMBER
RADIX NUMBER
CHARACTER_SET_NAME VARCHAR2(44)
TYPE_OWNER VARCHAR2(30)
TYPE_NAME VARCHAR2(30)
TYPE_SUBNAME VARCHAR2(30)
TYPE_LINK VARCHAR2(128)
PLS_TYPE VARCHAR2(30)
CHAR_LENGTH NUMBER
CHAR_USED VARCHAR2(1)
Look for Data_Type where IN_OUT say OUT. That will be the data type retruned by that function.
Edited :
or POSITION in argument list,or null for function return value
-SK
</FONT>
Maybe you are looking for
-
I cant seem to be able to transfer a recent purchase from itunes store to my ipad. Any ideas on how to transfer a hd tv show to my ipad? I have enough room for the download but get an error saying the ipad can not play back the video. Any thoughts or
-
Connection to Facebook via HTTPS fails
Hello everyone, I am trying to implement the Facebook API in CRM IC. To do so I followed SAP note 1832481. First, I downloaded a HTTPS certificate from facebook and uploaded it in transaction STRUST. Second, I implemented the API as described in the
-
Having trouble installing Flash 11.3 on Firefox
I was having trouble upgrading to the newest version of flash. I kept getting the error that flash was already running, but I'm pretty sure it wasn't. I read through the tips and saw it was suggested to uninstall and then reinstall flash. So I downlo
-
How is luminance calculated?
Hi, I'm using the Color Plane Extraction function on Vision Assistant to extract an the luminance plane of an image, but was wondering how exactly the luminance is calculated? Also, what is the difference between luminance and intensity? Thanks!
-
What Has Happened to Workflow in SharePoint 2013
I am at a loss to get workflow 2013 to work with SharePoint 2013. I am astonished that workflow (other than the broken and buggy 2010 version) is not part of SharePoint 2013. What on earth were they thinking. as if that is not bad enough they have ma